---
title: "Pause a ChatGPT Ads ad group"
method: POST
path: "/api/v1/tools/chatgpt_pause_ad_group/execute"
tags: ["ChatGPT Ads"]
---

# Pause a ChatGPT Ads ad group

`POST /api/v1/tools/chatgpt_pause_ad_group/execute`

## Request

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

Stops delivery on one ad group without touching the rest of the campaign. Spend on it drops to zero; nothing is deleted, the ads underneath keep their configuration and review history, and chatgpt_resume_ad_group starts it again.
Use when: the user wants to stop one part of a campaign — a test that is not working, an audience that is too expensive — and you have shown them what it is currently spending.
Do not pause on one or two days of data: this platform's daily numbers are noisy at small budgets. Show last_7_days from chatgpt_get_performance at ad_group level first.
Do not use this as a way to delete. Pausing is reversible; archiving is not.
Returns the ad group read back from the platform, which is how the pause is confirmed rather than assumed.

## Headers

- `Idempotency-Key` string

## Request body

- object
  - `arguments` object, required
    - `ad_account_id` string: ChatGPT Ads advertiser account id. One advertiser key belongs to one account, so this is only needed when the user has connected more than one key. Omit it to use the primary account.
    - `ad_group_id` string, required: The ad group to act on, from chatgpt_list_ad_groups.
    - `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)