---
title: "List TikTok pixels and their events"
method: POST
path: "/api/v1/tools/tiktok_list_pixels/execute"
tags: ["TikTok Ads"]
---

# List TikTok pixels and their events

`POST /api/v1/tools/tiktok_list_pixels/execute`

## Request

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

Lists the pixels on the advertiser account, the events each one is configured for, and whether TikTok reports the pixel as having any recent activity.
Use when: a campaign will optimise for conversions, the user asks whether tracking works, or a report shows spend with no conversions. Always call it before creating a WEB_CONVERSIONS campaign — the pixel id and event name it returns are the only valid values for that create.
Do not pick an event just because it exists. An event with no recent activity will not train TikTok's optimisation: the campaign stays in the learning phase, spends at a high CPA and never settles. Prefer an event firing at least a few dozen times a week, and say so if none does.
Do not conclude that ads are failing when every campaign reports zero conversions and this tool shows a pixel with no recent activity — that is a measurement problem, and pausing campaigns will not fix it.
Returns the pixel id and code, the events it can optimise for, and the standard event vocabulary TikTok accepts. TikTok publishes no per-event counts or timestamps on this endpoint, so "is it firing" is only answered at pixel level; confirm the specific event in TikTok Events Manager. Costs nothing.

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