Checks and help

Handle API errors

Read the status and fixed error code. Keep optional advertising separate from the model response.

Classify the result

A rejected request needs the cause corrected. An unchanged retry cannot repair a key, origin or consent mismatch. A successful response with decision.fill: false is No-Fill, not a transport failure.

Error codes and envelopes →

ResultNext action
401Check the app session and matching server key.
403Check exact origin, genuine consent and project permission. Do not bypass them.
400 / 409Correct the input or stale lifecycle state before a new attempt.
429Honor Retry-After when present. Retry only if the placement window remains valid.
5xx / timeoutKeep the model available, hide the empty slot and use bounded diagnostics.

Rate-limit response

Illustrative response. Read the actual status, body and optional Retry-After value.

Rate-limit response

429-rate-limited.http

text

HTTP
HTTP/1.1 429 Too Many RequestsRetry-After: 60{  "error": {    "code": "rate_limited",    "message": "Rate limit exceeded."  }}

Respect the placement window

Cancel obsolete requests and reject late results. No-Fill does not justify an automatic retry loop. For a During placement whose generation has ended, do not request another waiting-state ad.

Keep diagnostics useful and private

Record a request identifier, fixed error category and relative timing. Do not export keys, signed URLs, headers, cookies, prompts or conversations.

Troubleshoot the integration →

Need help with your integration?

Share the affected endpoint, request ID, and the behavior you expected. Leave out keys and user content.

Contact the team