API Rate Limiting Update
Posted: Thu Apr 17, 2025 10:06 am
What are we doing?
Simpro will be strictly enforcing the API rate limit of 10 calls/sec as of 17 April 2025 AEST. In August 2022, we announced the implementation of API rate limiting to our service. While the communicated threshold was 10 calls per second, Simpro was not proactively enforcing these limits in good faith; however, due to persistent and an increased number of API calls—sometimes exceeding 500 requests per second—we will begin enforcing rate limiting to mitigate the risk of system outages and slower performance.
2022 announcement: viewtopic.php?f=3&t=1876%5B/url%5D
API documentation: https://developer.simprogroup.com/apido ... a5a61fde9
Why are we doing this?
In the past, when the API rate limit was exceeded, it led to system problems, slower performance, and sometimes even system outages. To provide better service to our customers and partners, we will be strictly enforcing this rate limit. This will create clear limits on API access.
Enforcing rate limits is a standard practice for maintaining a reliable and scalable platform.
When will this change?
The API rate limit of 10 calls/sec came into effect on 9 August 2022.
We will be strictly enforcing this rate limit effective as of 17 Apr 2025 AEST.
Will I be affected?
If you see a ‘HTTP 429 Too Many Requests’ error. This means your integration makes a lot of requests at once, especially if it's executing concurrent multithreaded requests or submitting numerous small requests at a rapid pace. Our system data shows that this rate limit mainly affects integrations that make the highest number of requests. Therefore, most API applications should not be affected by this change.
If I do receive HTTP 429 responses, what can I do?
HTTP 429 error should be handled at an application level: queuing, sleep mechanism, backoff and retry logic etc. You can find more information on resolving this issue in this documentation: https://developer.simprogroup.com/apido ... ca5a61fde9
PLEASE NOTE: Rate limiting is per IP and per build.
Thanks for your understanding and support.
Simpro will be strictly enforcing the API rate limit of 10 calls/sec as of 17 April 2025 AEST. In August 2022, we announced the implementation of API rate limiting to our service. While the communicated threshold was 10 calls per second, Simpro was not proactively enforcing these limits in good faith; however, due to persistent and an increased number of API calls—sometimes exceeding 500 requests per second—we will begin enforcing rate limiting to mitigate the risk of system outages and slower performance.
2022 announcement: viewtopic.php?f=3&t=1876%5B/url%5D
API documentation: https://developer.simprogroup.com/apido ... a5a61fde9
Why are we doing this?
In the past, when the API rate limit was exceeded, it led to system problems, slower performance, and sometimes even system outages. To provide better service to our customers and partners, we will be strictly enforcing this rate limit. This will create clear limits on API access.
Enforcing rate limits is a standard practice for maintaining a reliable and scalable platform.
When will this change?
The API rate limit of 10 calls/sec came into effect on 9 August 2022.
We will be strictly enforcing this rate limit effective as of 17 Apr 2025 AEST.
Will I be affected?
If you see a ‘HTTP 429 Too Many Requests’ error. This means your integration makes a lot of requests at once, especially if it's executing concurrent multithreaded requests or submitting numerous small requests at a rapid pace. Our system data shows that this rate limit mainly affects integrations that make the highest number of requests. Therefore, most API applications should not be affected by this change.
If I do receive HTTP 429 responses, what can I do?
HTTP 429 error should be handled at an application level: queuing, sleep mechanism, backoff and retry logic etc. You can find more information on resolving this issue in this documentation: https://developer.simprogroup.com/apido ... ca5a61fde9
PLEASE NOTE: Rate limiting is per IP and per build.
Thanks for your understanding and support.