Rate limit

Provet REST API uses rate limits to throttle the amount of requests that a single REST API user can send in a certain period of time. This is done to manage the volume of requests and to protect server resources.

When you exceed the rate limit for an endpoint, the REST API will return a HTTP 429 Too Many Requests response to your request. Additionally, a Retry-After header is included in the response with a recommended amount of seconds to wait before attempting the request.

Rate limits are counted separately for each organization, API token, endpoint and kind of request: listing an endpoint (GET /client/) and reading one record from it (GET /client/3/) have separate limits. If your integration needs to use endpoints A with a rate limit of 100 requests/min and B with a rate limit of 200 requests/min, your integration would be able to make a total of 300 requests per minute between these two endpoints.

Rate limits for each endpoint are documented in the Provet REST API Schema.

Provet REST API evaluates the number of API requests by using a rolling 60-second window. After 60 seconds has elapsed since making the API request, the request will no longer count towards your limit.

A list request counts in steps of the endpoint’s default page size, which is 50 for most endpoints (see Paginated results). A page of up to 50 results counts as one request, 51 to 100 as two, and 500 as ten. What counts is the page size you ask for (after any limit the endpoint sets), not the number of results returned. Larger pages don’t let you read more results per minute, and pages smaller than the default use up the limit faster for the same number of results. See Keeping your data in sync for page sizes that work well.