Your campaigns.
Your tools. One API.
Bring Traffic Creator into your workflow. Read credit balances and track campaign delivery from your own applications.
Create your API key ↗
Connect securely with an account API key.
02 / BUILDMake your first request ↗
Start with a simple credit balance lookup.
03 / EXPLOREFind an endpoint ↗
Browse parameters and response schemas.
Authentication
Open Profile → Security & 2FA → API key to generate your read-only reporting key. Send it in the X-API-KEY header for the reporting endpoints below. These keys can only read your own balances and campaign statistics. Generating a new key replaces the previous one; revoke it from your profile at any time.
Your first request
Retrieve your remaining traffic credits. Replace YOUR_API_KEY with your key in your own terminal.
Professional credits are returned in credits.professional. Campaign totals and history are available through the reporting endpoints below.
API reference
Parameters and response schemas below come directly from this API’s Openpublic customer API specification. Examples use placeholders and do not execute requests.
Loading the API reference…
Usage limits
Each reporting key allows 60 reads per minute. Reporting access allows up to 4 concurrent reads per account; shared account and IP limits also apply. List up to 100 campaigns per page, query up to 90 days of daily history or 168 hours of hourly history. Reporting timestamps use UTC.
Retry-After before trying again. Keep the latest response in your application and avoid continuous polling. Do not automatically retry writes.Errors & troubleshooting
| Status | What to check |
|---|---|
| 401 / 403 | Check your API key and the permissions required by the endpoint. |
| 404 | Verify the campaign ID and that it belongs to your account. |
| 422 | Check the request fields and parameter types against the reference. |
| 429 | Reduce request frequency and retry after a delay. |
| 5xx | Retry with backoff. Contact support if the problem continues. |