API Rate Limiting
Posted: Tue Aug 09, 2022 7:33 am
Hi all,
In order to ensure the continued reliability and availability of the simPRO platform, we will shortly be introducing API Rate Limiting to our service.
The details of these limits can be found here
https://developer.simprogroup.com/apido ... ca5a61fde9
Why are we doing this?
In the past we have witnessed a few occurrences of an abusive API application causing performance issues for multiple customers, some even causing a "noisy neighbour" scenario where one customer's API application has caused performance issues for another customer who is hosted on the same infrastructure. We need to ensure that our customers are getting the service levels that they expect and that we strive for. The limit being put in place is high enough to still enable a very high level of integration possible, while protecting our systems from a flood of traffic.
Will I be affected?
If your integration makes multithreaded requests simultaneously, or very quickly makes many small requests, you may receive the HTTP 429 Too Many Requests response. After monitoring our systems in the past, most integrations will not fall foul of the current limit being imposed, only those that make the highest number of requests will. Most API applications will not need to worry about the rate limiting at all.
If I do receive HTTP 429 responses, what can I do?
First and foremost you should implement a backoff and retry logic to handle HTTP 429 responses.
In the documentation here
https://developer.simprogroup.com/apido ... ca5a61fde9
there are suggested approaches to requesting large amounts of data while still remaining below the call limit threshold. There are multiple ways to achieve the same desired outcome, some resulting in a lower volume of requests.
Thanks for your understanding and support.
Regards,
Rob Ormond
simPRO Group CTO
In order to ensure the continued reliability and availability of the simPRO platform, we will shortly be introducing API Rate Limiting to our service.
The details of these limits can be found here
https://developer.simprogroup.com/apido ... ca5a61fde9
Why are we doing this?
In the past we have witnessed a few occurrences of an abusive API application causing performance issues for multiple customers, some even causing a "noisy neighbour" scenario where one customer's API application has caused performance issues for another customer who is hosted on the same infrastructure. We need to ensure that our customers are getting the service levels that they expect and that we strive for. The limit being put in place is high enough to still enable a very high level of integration possible, while protecting our systems from a flood of traffic.
Will I be affected?
If your integration makes multithreaded requests simultaneously, or very quickly makes many small requests, you may receive the HTTP 429 Too Many Requests response. After monitoring our systems in the past, most integrations will not fall foul of the current limit being imposed, only those that make the highest number of requests will. Most API applications will not need to worry about the rate limiting at all.
If I do receive HTTP 429 responses, what can I do?
First and foremost you should implement a backoff and retry logic to handle HTTP 429 responses.
In the documentation here
https://developer.simprogroup.com/apido ... ca5a61fde9
there are suggested approaches to requesting large amounts of data while still remaining below the call limit threshold. There are multiple ways to achieve the same desired outcome, some resulting in a lower volume of requests.
Thanks for your understanding and support.
Regards,
Rob Ormond
simPRO Group CTO