Limits & errors
Request limits
Section titled “Request limits”| Limit | Documented value |
|---|---|
| API request rate | 1,000 requests per minute, measured over a sliding 60-second window. |
| Time series date range | At most 180 days per request. |
| IDs in a lookup | At most 50 per request. |
| Discovery partitions | Between 100 and 10,000. |
| Discovery page size | Up to 500 records per page. |
| Export URL lifetime | 24 hours after the API request. |
Your dataset access and historical coverage depend on your subscription.
Handle unsuccessful requests
Section titled “Handle unsuccessful requests”| Status | Next step |
|---|---|
400 |
Check query names, date formats, required fields, and JSON syntax. |
401 |
Check the raw Authorization token and authenticate again if it expired. |
403 |
Verify that your account can access the requested dataset. |
404 |
Check the route and store name. |
429 |
Slow down and retry with exponential backoff and jitter. Respect Retry-After when supplied. |
5xx |
Retry a read request with backoff. Contact support if failures persist. |
Avoid retrying an unchanged invalid request in a tight loop. The playground sends one request at a time and displays the HTTP status and response body.
Browser requests
Section titled “Browser requests”The playground calls the API directly from your browser. A network error may indicate a connection problem or a CORS policy that prevents access from your current origin. Copy the cURL, Node.js, or Python example to run the same request outside the browser.
Contact support
Section titled “Contact support”Send your Apptopia contact the route, store, non-sensitive query parameters, HTTP status, request ID if available, and the expected result. Remove credentials, authorization headers, and private response data before sharing a reproduction.