To protect the stability of the platform and prevent undue stress on the system, Data APIs may return 429 Too Many Requests when requests are throttled. Integrations should be built to handle this response.
If the response includes a Retry-After header, wait at least the indicated number of seconds before retrying. If the header is absent, consider using exponential backoff; wait before retrying, then increase the delay after each consecutive 429 response. Limit the number of retries.
Refresh and upload constraints
Refresh intervals and upload-size limits depend on the applicable subscription and configuration. Do not assume the same settings apply to every user.
| Constraint | Meaning |
|---|---|
| Hard Refresh Interval | The configured interval between full data refreshes |
| Soft Refresh Interval | The configured interval between incremental data refreshes |
| File Size Limit | The configured maximum upload size |
Use Get Rate Limits to retrieve the settings currently applicable to the requesting user.