Appearance
Limits, retries & errors
Limits are shared across your account’s tokens, HTTP and MCP. Server settings may lower these ceilings.
| Account budget | Hour | Day |
|---|---|---|
| Reads | 2,000 | 8,000 |
| Data/analysis requests | 120 | 480 |
| Source bytes | 1 GiB | 4 GiB |
| Response bytes | 128 MiB | 512 MiB |
Burst limits are 120 reads/minute and 10 data/analysis reads/minute.
Download efficiently
Use larger permitted pages and cache completed downloads. Failed or repeated requests may still consume budget. The same unchanged GPS page can be read only three times/hour/account.
On 429, wait for Retry-After. Budget errors include the affected budget, remaining allowance and reset time. If a wait outlasts a cursor’s 15-minute lifetime, restart only the unfinished track.
For mutation retries, keep the same Idempotency-Key and input.
Common errors
| Status | What to do |
|---|---|
| 401 | Check or replace the token. |
| 403 | Check your subscription, scopes and resource access. |
| 404 | Check the returned ID and feature availability. |
| 409 | Inspect the reason; refresh source or request state. |
| 422 | Correct the request inputs. |
| 429 | Wait for Retry-After. |
| 503 | Retry later with backoff. |
When contacting support, include X-SailSync-Usage-ID, not your token.
