The API employs a number of safeguards against bursts of incoming traffic to help maximize its stability. Users who send many requests in quick succession may see error responses that show up as status code 429.
We generally allow up to 5 requests per second, though this may change at any time. The request limit is scoped per user or IP address if no user identifier is available. If you need more please get in touch with our support.
There is also a concurrency limit when it comes to creating or updating visits for a location. If too many concurrent requests happen the server will respond with status code 409. The request may then be retried.
Please treat these limits as maximums and don’t generate unnecessary load. We may adjust limits to prevent abuse or enable well-behaved high-traffic applications. A basic technique for integrations to gracefully handle limiting is to watch for 429 status codes and build in a retry mechanism. The retry mechanism should follow an exponential backoff schedule to reduce request volume when necessary. We’d also recommend building some randomness into the backoff schedule to avoid a thundering herd effect.
Updated over 2 years ago