---
title: "Check whether a campaign actually exists and is running"
method: POST
path: "/api/v1/tools/verify_campaign_is_live/execute"
tags: ["Adako"]
---

# Check whether a campaign actually exists and is running

`POST /api/v1/tools/verify_campaign_is_live/execute`

## Request

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

Answers one question with real data: does this campaign exist, is it switched on, and does it have a budget it can spend? Free when Adako has synced history for the account; otherwise it falls back to the platform's own list tool, which is free too, and says which source it used.
Use when: a create or a resume has just run and the user wants proof; the user says "nothing is spending"; or you need to confirm state before proposing another change.
When not to use: the user wants performance numbers — this is an existence and status check, not a report.
Returns exists / status / budget / whether it should be serving, with what to do when it is not. It never changes anything, and never claims a campaign is live without having read it back.

## Headers

- `Idempotency-Key` string

## Request body

- object
  - `arguments` object, required
    - `platform` 'google_ads' | 'meta_ads' | 'chatgpt_ads' | 'tiktok_ads' | 'linkedin_ads', required: Which ad platform the campaign is on.
    - `campaign_id` string, required: The campaign id, as a string, exactly as the platform returned it.
    - `account_id` string: Ad account id. Defaults to the primary active account on that platform.

## 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)