Maropost API Limits
Our limits were the result of a longitudinal study of API usage across our entire client base. We arrived at a limit that is consistent with industry standards, while creating minimal impact on our clients.
Our analysis has revealed that the majority of API calls are completed in approximately 300 milliseconds. As a result, Maropost has set a limit of 10 concurrent calls per account.
What happens if a web service call to Maropost exceeds the limit?
Maropost’s API server will respond with an HTTP Status Code 429. According to RFC 6585, “The 429 status code indicates that the user has sent too many requests in a given amount of time (“rate limiting”).”
In the event that an HTTP Status Code 429 is received in response to an API method call, it is up to your development team to implement the proper response handling. Caching, queuing, and retrying requests for web services is a common implementation.
Why is Maropost enforcing rate limiting of its web services?
Rate limiting of web service consumption is an industry standard, and the definition of rate limits varies from company to company. Web services are shared resources. Rate limiting prevents a handful of clients from monopolizing resources, and ensures that everyone has equal opportunity for use.
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 it, please email our Customer Success team at Success@maropost.com, to be connected with the appropriate person.