Practical guides
Understand errors
Find the cause of a failed request and the next step.
| Response | What to check |
|---|---|
401 Unauthorized | Is the bearer key present, valid, unexpired and not revoked? |
403 Forbidden | Does the key have the required scope, token type and workspace access? Is Public API access enabled? |
404 Not Found | Are the workspace and resource IDs correct and accessible to this key? |
409 Conflict | Does the campaign's current state allow this action? Read the endpoint's preconditions. |
422 Unprocessable Entity | Check required fields, supported values and the error message. |
429 Too Many Requests | Follow request limits and retry guidance. |
The request was accepted, but the action failed
An HTTP 202 starts background work. Read the operation result for failures such as failed_precondition, resource_exhausted or provider_failed. Do not report completion based on the initial response.
For write retries, reuse the original Idempotency-Key and identical request body where the endpoint supports it. A new key may start a second action.
Contact support
Include the request ID when available, endpoint, time, HTTP status and error code/message. Remove API keys, signing secrets and private lead data. Never send the full Authorization header.