Testing
Simulating errors
Test auth, origin, rate-limit, validation, and unknown project failures.
Auth failures
Call a secret-key endpoint without auth and with a publishable key. Expect actionable 401 or 403 errors.
Origin mismatch
Use a publishable key from an unlisted origin and confirm the runtime forbidden error is visible to the developer.
Rate limits
Use a controlled local 429 response to verify Retry-After handling. Do not flood the public API or reset a server limit to test the retry branch.
Expected negative tests
Intentional sandbox checks for missing asset_token, missing slot_id, invalid event, stale occurred_at, or invalid consent purpose should return actionable 400 validation errors with request IDs and field paths. These are not production integration failures when deliberately triggered.
Stale direct server beacon timestamps can return BEACON_TOO_LATE. Generate occurred_at at runtime with new Date().toISOString() for every beacon event.
Need help with your integration?
Share the affected endpoint, request ID, and the behavior you expected. Leave out keys and user content.