---
title: "Pause a TikTok ad"
method: POST
path: "/api/v1/tools/tiktok_pause_ad/execute"
tags: ["TikTok Ads"]
---

# Pause a TikTok ad

`POST /api/v1/tools/tiktok_pause_ad/execute`

## Request

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

Stops delivery on one TikTok ad by setting its operation status to DISABLE. Spend stops; nothing is deleted, everything underneath keeps its configuration and history, and it can be started again with tiktok_resume_ad.
Use when: the user has explicitly asked to stop this ad, and you have shown them what it is currently spending.
Do not pause on one or two days of data — TikTok's daily numbers swing hard and pausing resets the learning the ad group has accumulated, which costs more than the bad day did. Show last_7_days first.
Do not use this as a way to delete. Pausing is reversible; TikTok's DELETE is not, and no Adako tool sends it.
Do not pause a ad that is merely expensive without checking why: tiktok_analyze_wasted_spend separates "spent with nothing to show" from "still learning".
Returns the ad read back from TikTok, which is how the pause is confirmed rather than assumed.

## Headers

- `Idempotency-Key` string

## Request body

- object
  - `arguments` object, required
    - `advertiser_id` string: TikTok advertiser id (a long numeric string). Only needed when the user has authorised more than one advertiser. Omit it to use the primary one.
    - `ad_id` string, required: The ad to act on, from tiktok_list_ads.
    - `idempotency_key` string: Optional caller-supplied key; identical keys never execute twice.
    - `raw_data` boolean: Return compact JSON only (no markdown). Use when you will compute on the result.

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