Rate Limits and Errors

Updated today

Over your per-key limit the API answers 429 with Retry-After. Every status code, and what to do about it, is below.

Rate limits

Limits are per key, per minute, set when the key is issued. Over the limit the API answers:

HTTP/1.1 429 Too Many Requests
Retry-After: 23

{ "error": "Too Many Requests", "retry_after_seconds": 23 }

Wait Retry-After seconds and retry the same request; nothing was written. The window is a fixed calendar minute, so a burst that straddles the minute edge can briefly exceed the limit. If you need a higher limit, ask TrackFlo.

Status codes

Code	Meaning	What to do
`200`	Accepted. Read `status`: `processed`, `skipped` or `duplicate`.	Nothing. `skipped` and `duplicate` are normal, not errors.
`400`	Malformed JSON or a missing required field; `error` names it.	Fix the body. Do not retry unchanged.
`401`	Missing or unknown `X-API-Key`.	Check the header and that the key is still active.
`403`	The body or URL names a tenant other than the key's.	Check `company_permalink` and every `*_permalink` suffix.
`429`	Rate limit.	Wait `Retry-After` seconds, retry.
`500`	Unexpected failure; the body carries an `error_id`.	Retry with backoff. If it persists, send the `error_id` to TrackFlo.

The 200 envelope

{ "status": "processed", "message": "Load processed", "permalink": "1083452-acme" }

`status`	When
`processed`	Stored (created or updated).
`skipped`	Left unchanged: the record changed in TrackFlo after your `sync_run_time`, or the carrier's contacts are managed inside TrackFlo.
`duplicate`	A load update whose permalink was already stored.

Was this helpful?