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 adetail 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:
Retrying
On429, 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.
Related
- Authentication - what a
401and a403mean for each header - Rate limits - the limit behind a
429, and the headers that track it - Idempotency - retrying a write without duplicating it
- Find the source of an error - when the failure is on the sync rather than your request