REST API · Structure
List ads
Ads of the ad account, optionally of one campaign or ad set
GEThttps://api.apogee.ad/api/v1/ad-accounts/{acc}/ads
What it does
platform tiktok / snapchat: that platform's ads (adset_id = a TikTok ad group / a Snapchat ad squad).
Request
GET /ad-accounts/{acc}/ads on https://api.apogee.ad/api/v1.
Path parameters
-
accstring path requiredAd account id: Meta act_…, a TikTok advertiser id or a Snapchat ad account id (GET /ad-accounts?platform=…)
Query parameters
-
limitinteger query optionalPage size
-
cursorstring query optionalnext_cursor of the previous page
-
searchstring query optionalFilter on the name (contains, case-insensitive)
-
campaign_idstring query optional -
adset_idstring query optional -
platformstring query optionalmeta (default), tiktok or snapchat
Headers
-
Authorizationstring header requiredBearer apk_…: an API key with the scope of this route.
Response
200. A page of results: pass next_cursor as cursor for the next one, limit from 1 to 200 (default 50).
-
dataarray of objectsFields of each item (3)
-
idstring -
namestring or null -
statusstring or null
-
-
has_moreboolean -
next_cursorstring or null
Every answer carries X-Request-Id (give it to support), Apogee-Version: 2026-10-06, and the RateLimit and RateLimit-Policy headers.
Errors
Errors are application/problem+json with a stable code to switch on (all the codes).
| Status | Possible codes |
|---|---|
| 400 Bad request | idempotency_key_required, not_supported, request_refused, validation_failed |
| 401 Unauthorized | invalid_api_key |
| 403 Forbidden | account_not_connected, forbidden, insufficient_scope, meta_permission_denied, platform_permission_denied, upgrade_required |
| 404 Not found | not_found |
| 412 Precondition failed | drive_not_connected, meta_not_connected, platform_not_connected |
| 429 Too many requests | daily_read_cap, meta_rate_limited, platform_rate_limited, quota_exceeded, rate_limited |
| 500 Internal server error | internal_error |
| 502 Bad gateway | drive_error, launch_failed, meta_error, platform_error, upstream_error |
Example
With your key in APOGEE_API_KEY (create one):
curl 'https://api.apogee.ad/api/v1/ad-accounts/act_1234567890/ads' \
-H "Authorization: Bearer $APOGEE_API_KEY" {
"data": [
{
"id": "120200000000000001",
"name": "Nordlicht | Spring launch",
"status": "ACTIVE"
}
],
"has_more": false,
"next_cursor": null
} Access and cost
| Plans | Pro and Scale. |
|---|---|
| Scope | read (scopes). |
| Credits | Free up to the daily free reads (5,000 a day on Pro, 10,000 on Scale), then 1 credit per read. A request that fails costs nothing, a replayed one neither (credits). |
| Rate limit | Read: 600 per 15 minutes on Pro, 1,200 on Scale (rate limits). |
| Meta budget | Reads Meta: spends 1 unit of the account's Meta budget (1,800 per 15 minutes, 900 per ad account). |
| Daily cap | Counts 1 unit toward the 2,000 units one API key can use in 24 hours. |
In the MCP
An AI assistant does the same with this tool of the MCP server:
list_ads: The ads of an ad account, a campaign or an ad set (200 at most).
Related operations
- List campaigns:
GET /ad-accounts/{acc}/campaigns - List ad sets:
GET /ad-accounts/{acc}/adsets - Get latest in campaign:
GET /ad-accounts/{acc}/campaigns/{id}/latest - Get an ad set template:
GET /adsets/{id}/template - Get ad template:
GET /ads/{id}/template