Skip to main content
Every failed request returns a status code and a detail field. Bindbee serves your reads from its synced copy, so a source system failing surfaces on the sync instead of here - see Find the source of an error.

Status codes

Retrying a 4xx other than 429 never succeeds, and consumes the connector’s rate limit while failing. For what causes a 401 or a 403 specifically, see Authentication.

The response body

Every error carries a detail field, and its type depends on the status. On 401, 403, 404 and 429 it is a string. On 422 it is an array, one entry per rejected field:
The same key holds two types. Code that treats detail as a string works against every other status and throws on the first 422. Branch on the status before touching detail.

Retrying

On 429, wait the number of seconds in Retry-After - see Rate limits for the limit and the headers that track it. On 5xx, retry with exponential backoff and jitter, capped at a few attempts.
Retry a write only with X-Idempotency-Key. A 5xx can be returned after the record was created upstream - see Idempotency.