Rate limiting

The Pexip Engage REST API implements rate limiting as a way to ensure stability, reliability, and security. This means that developers need to keep in mind that there are limits to the number of requests that can be made in a given period of time.

The specific rate limits for our API are subject to change and may vary depending on the specific endpoint being accessed. Currently, a maximum of 3,000 requests per minute and 4 concurrent requests are allowed from a single IP address.

When a rate limit is exceeded, the API will respond with a 429 HTTP status code.

To cope with rate limiting, the following measures can be taken:

  • Implement queuing to perform API calls asynchronously in a sequential order (e.g., using RabbitMQ, Apache Kafka, ...)
  • Implement exponential backoff to handle rate limiting errors