Rate limits

To ensure fair usage of our APIs, we employ rate limiting. Currently, the general limit is 500 requests/minute per API key.

A few of our APIs have stricter limits. These are limited to 120 requests/minute per API key, and are counted separately. Currently, the following APIs are subject to the stricter limits:

• Observations API
• Relations API (Ownership structure)

How are requests counted?

The rate limit works in such a way that the first request starts the request window, which resets after one minute. Once exceeded, you must wait the number of seconds indicated in the Retry-After header before making another request.

Once you exceed the limit, you will receive the following response with a 429 status code:

{
    "errorMessage": "Too many requests. We allow 500 requests per minute.",
    "httpStatusCode": 429,
    "errorCode": 26,
    "friendlyError": "Please retry your request after the seconds indicated in the 'retry-after' response-header.",
    "helpMessage": "For more information about rate limiting, visit our documentation.",
    "helpLink": "https://docs.lassox.com/api/getting-started/rate-limits/"
}

Suggestions for handling limits

There are several steps you can take to properly handle a rate-limited request. As the friendlyError field indicates, you will receive a response header named Retry-After, containing the number of seconds you must wait before sending another request.

You can also monitor the current number of remaining requests on successful responses by checking the X-Rate-Limit-Remaining response header. Additionally, you can use the X-Rate-Limit-Reset response header to determine when your limit will reset.

We strongly advise you to not hardcode limits in your app, but to instead read the values directly from the response headers. That way, you won't need to update your code if our limits change in the future.