Adako

Pause, resume or delete a scheduled brief or a monitor

Pauses, resumes or deletes one recurring brief or one monitor. Adako settings only; nothing on the ad platform changes, past reports stay readable and proposals a monitor already made stay in the approvals inbox. Use when: the user says a brief is too frequent, an alert is too noisy, or wants either one back. Name what you are acting on: task_id for a brief, monitor_id for a monitor. Both come from list_scheduled_tasks; monitor ids also come from list_monitors. Pass one, never both. Prefer pause over delete: a paused brief keeps its settings, a paused monitor keeps its history, and either resumes in one call. Deleting needs confirm_delete: true — a schedule cannot be recovered and a deleted monitor takes its evaluation history with it. Do not use when: the user wants a monitor's threshold or rule changed — that is update_monitor. Returns the new state of whichever one you named. If you are unsure whether the user means a brief or a monitor, call list_scheduled_tasks and ask.

post/api/v1/tools/manage_scheduled_task/execute

Request

  • Base URL: https://adako.ai
  • URL: https://adako.ai/api/v1/tools/manage_scheduled_task/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.