Rate-limiting and throttling on the ReflexBlue External API

Most endpoints of the ReflexBlue External API are subject to rate-limiting (also known as throttling). This means that within a certain period, you can only send a limited number of requests to these endpoints. External systems must take this into account and temporarily postpone requests if the limit is reached.

Exceeding the limit

If you exceed the limit, the ReflexBlue Application Server will return an HTTP status code 429 (Too Many Requests) when making a request to the External API. In the response, you will find the HTTP header retry-after. This header indicates how many milliseconds you must wait before you can make a new request.

The external system can then temporarily pause processing. Once the specified time has passed, you can send a request again.

Allowed number of requests

Usually, you may send up to 60 requests per minute to the ReflexBlue Application Server via the External API. However, this number may vary per API endpoint and depends on other factors. Therefore, always check the documentation of the specific endpoint for the current limits.

Exceptions to rate-limiting

Certain API endpoints are exempt from rate-limiting. Check the documentation of the relevant endpoint to see if rate-limiting applies.