Observe errors, pagination and limits

Check the HTTP status and the error response documented on each endpoint. Correct invalid requests before retrying them.

Status	What to check
`400`	Required fields, field formats and endpoint-specific filter constraints
`401`	Missing, invalid or expired API key, a source IP outside the key’s allow list or a missing permission; the error message names the cause
`403`	A feature that is not enabled for the project, or SDK collection from an origin that is not authorized
`404`	Resource ID and the project selected by the API key
`429`	Concurrency or capacity limits; honor `Retry-After` when present
`5xx`	A server or delivery failure; retry reads with backoff

Before retrying a write, determine whether the first request took effect. In particular, check export or deletion job status when you already have a job ID.

Pagination

Pagination is endpoint-specific. Paged lists can return X-Corbado-Page, X-Corbado-TotalPages and X-Corbado-TotalItems. Search endpoints can instead use a limit and time or identifier filters. Follow the selected endpoint’s parameters and response headers; do not assume every search returns page counts.

Busy responses and exports

Time-series and funnel reads can return 429 with Retry-After when capacity is temporarily unavailable. Wait for the indicated delay before retrying. A project can run two time-series exports concurrently. Creating an export streams progress over the request; keep the connection open until completion or failure. After a disconnect, inspect the export status before starting it again. Use the export guide for supported intervals, date ranges and download behavior.

Overview

Corbado Observe

Corbado Connect

Observe errors, pagination and limits

Busy responses and exports

​Pagination

​Busy responses and exports

Pagination

Busy responses and exports