---
title: "List TikTok identities the ads can post as"
method: POST
path: "/api/v1/tools/tiktok_list_identities/execute"
tags: ["TikTok Ads"]
---

# List TikTok identities the ads can post as

`POST /api/v1/tools/tiktok_list_identities/execute`

## Request

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

Lists the identities this advertiser can run ads as — the handle and avatar a viewer sees on the ad — including the custom identities created in Ads Manager and any TikTok accounts authorised through Business Center.
Use when: creating any ad, and always before a Spark Ad. A Spark Ad runs as the account that posted the original video, so it needs that account's identity id and its permission; without both, the create fails.
Do not pick an identity for the user when several exist. Which account an ad appears as is a brand decision and a legal one — ask.
Returns can_push_video, which is what distinguishes an identity that can carry a real TikTok post from a display-only custom identity, and the Business Center id a BC_AUTH_TT identity needs passed as identity_authorized_bc_id. TikTok no longer accepts new ads that post as a custom identity (CUSTOMIZED_USER) on placements that include TikTok, so offer a TikTok account identity.
Costs nothing, and the answer rarely changes, so read it once per launch rather than per ad.

## Headers

- `Idempotency-Key` string

## Request body

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