Rate Limits and Errors
Updated 3 weeks ago
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
Every key has a limit 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.
Planning a backfill or a full resync? Ask us to raise your limit first. A new limit takes effect within a minute.
Status codes
Code | Meaning | What to do |
|---|---|---|
| Accepted. Read | Nothing. |
| Malformed JSON or a missing required field; | Fix the body. Do not retry unchanged. |
| Missing, unknown, deactivated or expired | Check the header. If the key has expired or been deactivated, ask us for a new one. |
| The body or URL names a tenant other than the key's, or the key type is invalid for the endpoint. | Check |
| Rate limit. Nothing was written. | Wait |
| Unexpected failure; the body carries an | Retry with backoff. If it persists, send the |
The 200 envelope
{ "status": "processed", "message": "Load processed", "permalink": "1083452-acme" }
| When |
|---|---|
| Stored (created or updated). |
| Left unchanged: the record changed in TrackFlo after your |
| A load update whose permalink was already stored. |