Adako

Approve or reject a change a monitor proposed

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.

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

Headers

Idempotency-Keystring

Optional 8-128 character key. A successful envelope is cached for 24 hours; replaying the key with the same arguments returns it again with Idempotent-Replayed: true, and replaying it with different arguments answers 409.

Request body

Response

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

successunknown required
toolstring required
dataobject required

Machine-readable result.

markdownstring required

The same result written for a person or a model.

proposal_idstring

Present for writes. Nothing changes on the ad platform until it is approved.

approve_urlstring

Where a person approves the proposal.

request_idstring required

Changes

No recorded changes to this operation across all 1 revision of this API.