Ad Launcher
Ad Launcher rate limits
How the Ad Launcher API splits read and write traffic into separate rate-limit buckets.
The Ad Launcher API uses two independent rate-limit buckets, each keyed per authenticated user.
General bucket
- Applies to: every lookup endpoint (
ad-accounts,adsets,ad-profiles,businesses,catalogs,leadgen-forms), the creative upload handshake (POST /creatives,POST /creatives/{id}/complete, multipart variants),GET /launches/{batchId}andGET /launches/{batchId}/export. - Default: ~100 requests / 60 s per API key. Configurable per org.
- Quota source:
api_rate_limit_config.generalAPI.
This bucket is shared with the Manage and Analytics APIs.
Launch (write) bucket
- Applies to:
POST /launchesonly. - Default: much stricter than the general bucket, set deliberately low. Configurable per org.
- Quota source:
api_rate_limit_config.adnova_ad_launcher.
The buckets are separate, so POST /launches traffic does not eat into your read-endpoint budget, and vice versa.
Response headers
Every response carries the standard IETF RateLimit-* headers.
RateLimit-Limit: 100
RateLimit-Remaining: 87
RateLimit-Reset: 23When exceeded, the API returns 429:
{
"error": {
"code": "RATE_LIMIT_EXCEEDED",
"message": "Rate limit exceeded"
}
}Polling guidance
POST /launches returns retryAfterSeconds in the body — respect it. Polling GET /launches/{batchId} faster than that just burns your general bucket; it does not speed up processing.
