sloe/ developers
Operate your integration

Errors, limits and retries

Handle failures explicitly and keep imports recoverable.

StatusLikely meaningWhat to do
400Unsupported or missing parameters; invalid query-key authValidate against the endpoint schema
401Missing, invalid, expired or revoked authenticationReconnect or verify the server-side key
403Account or feature is not entitledCheck access; do not retry unchanged
404Institution, resource or dataset was not foundCheck identity; do not invent an empty record
409Pinned release or source version cannot be served consistentlyDiscard the partial import and restart from page one
429Rate limit reachedHonor Retry-After when present; reduce concurrency
5xxServer or source is unavailableRetry briefly with backoff, then surface the failure

A successful response uses ok: true. Errors use ok: false and an error value; a trace_id is included when available. Keep the HTTP status and safe trace ID for support. Do not assume every failure response has the same JSON shape: an upstream or hosting error may return another content type.

Bounded retry policy

For idempotent reads, use a timeout, exponential backoff with jitter and a small maximum attempt count. Do not retry all status codes. Persist the job's failed state instead of looping indefinitely. A signed single-use download token should be replaced with a fresh broker request after expiry or a failed redemption.

Limits vary by endpoint. Institution search currently caps responses at 200 records and applies 90 requests per minute per key; other endpoint and authentication limits also apply. Do not treat a page-size limit as a throughput guarantee.

Report a problem

Include the route name, HTTP status, approximate UTC time and trace ID if returned. Redact credentials and confidential customer exports. Never send your API key in an email or screenshot. Contact Sloe.

On this page