Our API request limit is a result of a longitudinal study of API usage across our entire client base. Our analysis revealed that the majority of API calls get completed in approximately 300 milliseconds. Keeping that in mind, we arrived at the limit that is consistent with industry standards while having minimal impact on our clients.
The API request limit is set as 10 concurrent calls per account. Note that there is currently no limits defined for total API calls over a span of 24-hours.
Frequently Asked Questions
Why is Maropost enforcing a request limit for its web services?
While the definition of rate limits varies from company to company, the rate limiting of web service consumption is an industry standard practice. This practice prevents monopolization of resources and ensures everyone gets equal access to the web services.
What happens when you exceed the API call request limit?
On exceeding the request limit, the Maropost API server responds with an HTTP status code 429. The Internet Engineering Task Force (IETF) defines the status code as following: "The 429 status code indicates that the user has sent too many requests in a given amount of time ("rate limiting")." Refer RFC 6585 to read more about the HTTP status code.
You must implement the response handling in your application code.
If you would like to discuss further whether Maropost’s rate limiting will impact your consumption of our web services, please contact your Customer Success Manager. If you do not know who that person is, please email our Customer Success team at Success@maropost.com to be connected with the appropriate person.