---
title: "Approve or reject a change a monitor proposed"
method: POST
path: "/api/v1/tools/manage_action/execute"
tags: ["Adako"]
---

# Approve or reject a change a monitor proposed

`POST /api/v1/tools/manage_action/execute`

## Request

- Base URL: `https://adako.ai`
- URL: `https://adako.ai/api/v1/tools/manage_action/execute`
- Auth: HTTP bearer

Applies or declines one proposal that a monitor created. Approving executes it exactly once against the ad platform and reads the object back; rejecting marks it so it can never execute.
Use when: the user has explicitly said yes or no to the specific change — quote its summary from list_pending_actions first.
Do not use when: the user is still deciding, or the proposal came from a tool call they made themselves (use approve_proposal / reject_proposal, which say the same thing in that context).
Approving is real money: a pause stops delivery, a budget cut changes what the campaign can spend. If the proposal expired or was already decided, this returns an error — say so rather than silently recreating it.

## Headers

- `Idempotency-Key` string

## Request body

- object
  - `arguments` object, required
    - `proposal_id` string, required: Id from list_pending_actions.
    - `action` 'approve' | 'reject', required: approve applies the change; reject retires the proposal.
    - `reason` string: Why it was rejected. Stored with the proposal; it improves later proposals.

## Response `200`

The tool ran. A write returns proposal_id and approve_url while the change waits for approval.

- SuccessEnvelope
  - `success` unknown, required
  - `tool` string, required
  - `data` object, required: Machine-readable result.
  - `markdown` string, required: The same result written for a person or a model.
  - `quota` Quota: Task usage for the current billing period.
    - `plan` string
    - `used` integer
    - `limit` integer
    - `period_end` string
    - `upgrade_url` string
  - `proposal_id` string: Present for writes. Nothing changes on the ad platform until it is approved.
  - `approve_url` string: Where a person approves the proposal.
  - `request_id` string, required

## Other responses

- `400`: Invalid arguments, or the ad account could not be resolved.
- `401`: Missing, invalid, revoked or expired API key.
- `402`: Monthly task quota used up, or the plan does not include this tool.
- `403`: The connected ad account lacks the access level this tool needs.
- `404`: Unknown tool name.
- `409`: Not connected, reconnect needed, confirmation required, a proposal already pending or no longer pending, an identical create that failed earlier today (proposal_failed_before), a create that duplicates an approved one (duplicate_create), the ad-account limit of the plan reached (account_limit), or an Idempotency-Key reused with different arguments.
- `429`: Rate limited by Adako or by the ad platform. See Retry-After.
- `500`: Unexpected error inside Adako.
- `502`: The ad platform returned an error.

---

[API](https://skmtc.dev/adako/apis/adako-rest-api.md) · [All operations](https://skmtc.dev/adako/apis/adako-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/adako/apis/adako-rest-api/revisions/59ee60d48a56?raw)