---
title: "Show the connected ChatGPT Ads account"
method: POST
path: "/api/v1/tools/chatgpt_get_account/execute"
tags: ["ChatGPT Ads"]
---

# Show the connected ChatGPT Ads account

`POST /api/v1/tools/chatgpt_get_account/execute`

## Request

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

Reads the advertiser account the stored key belongs to: id, name, website, currency, timezone, account status and the platform's review verdict on the account. This is the same call the key was verified with when the user connected it.
Use when: starting work on this platform, confirming which account you are about to change, or checking whether a failing call is an access problem rather than a data problem. Run it before any write if you are not certain which account the key points at.
Do not use it to see what is running — that is chatgpt_list_campaigns. Do not use it to test a key the user pasted into chat: keys are only ever stored through the Accounts page and are never passed to a tool.
Returns the account currency and timezone. Every budget and every spend figure on this platform is a decimal in that currency, and every reporting window is resolved in that timezone. If the account review status is not "approved", nothing will deliver no matter what is created — say so before building anything.
Costs nothing, so run it whenever the answer would otherwise be a guess. If it fails with a reauth error the key was rotated or revoked and the user must paste a new one.

## Headers

- `Idempotency-Key` string

## Request body

- object
  - `arguments` object
    - `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.
    - `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)