Getting Started
Errors & Status Codes
All API errors return a JSON body with an error key describing what went wrong. HTTP status codes follow standard REST conventions.
Error response format
Error envelope
{ "error": "Human-readable description of what went wrong" }
HTTP Status Codes
CodeNameWhen it occurs
200
OK
Request succeeded. Also returned on re-application after rejection cooldown (not 201).
201
Created
Resource created successfully. Returned when a new access request is submitted.
401
Unauthorized
Missing or invalid API key. Check your Authorization header format:
Token YOUR_KEY
403
Forbidden
Your API key doesn't have the scope required for this endpoint.
404
Not Found
The requested resource doesn't exist, or has been paused/deleted.
422
Unprocessable Entity
Request validation failed. The error message explains the specific reason (e.g. already applied, campaign not accepting requests).
429
Too Many Requests
Daily limit reached (e.g. access requests or channel creation). The response includes
limit, used, and resets_at alongside error. Retry after the reset time.
500
Server Error
Something went wrong on our end. Please retry. If persistent, contact support.
Common 422 messages
MessageEndpointReason
Campaign is open - no access request needed
request_access
Campaign is approved_for_all. Just use the tracking URL.
Access request already pending
request_access
You've already applied. Wait for the advertiser to respond.
Campaign access already approved
request_access
You already have access. No need to re-apply.
You can re-apply after June 22, 2026
request_access
Your application was rejected. 3-month cooldown applies before re-applying.
Channel not found or does not belong to you
request_access
The channel_id you passed either doesn't exist or belongs to another publisher.