Skip to main content

What are rate limits?

Overview of what are rate limits and how to make sure that your store isn't affected by them

Written by Laura from Montonio

In this article we'll cover what are rate limits. And what steps to take to avoid your store being hit by rate limits.

What is rate limiting?

Every API has limits on how many requests it can handle in a given time window. Rate limiting is the mechanism that enforces those limits — once a threshold is reached, further requests are rejected until the window resets.

For Montonio, rate limits apply to our API endpoints — including payment initiation, order status checks, and webhook interactions. Exceeding the limit means your requests will return an error (typically HTTP 429 Too Many Requests) until the window resets.

By default, Montonio allows up to 1,500 requests per 5-minute window per merchant.


What to do if you expect higher volumes?

If your business is growing, for example you're running a promotion, entering a peak season like Black Friday, or scaling up transaction volume, reach out to Montonio before it happens.

We can review your integration, assess your expected volume, and adjust limits proactively so your customers never experience a disruption.

Contact us at: [email protected]

When you reach out, it helps to share:

  • The timeframe you're anticipating higher volumes

  • Your expected peak request volume

  • The specific endpoints you rely on most (e.g. order creation)

Proactive communication is always better than reactive firefighting. We'd rather raise your limits ahead of time than have your checkout go down during your biggest sale of the year.


What to do if you've already hit the rate limit?

If you're seeing 429 errors in your logs or your integration has stopped working unexpectedly, you may have hit your rate limit.

Contact us at [email protected] and include:

  • Your store/business name

  • The endpoint(s) returning 429 errors

  • Approximate time the issue started and the volume you were sending

Our team will investigate, help you understand what triggered the limit, and work with you on a resolution — whether that's a temporary limit increase or guidance on optimising your API call patterns (e.g. caching order status instead of polling repeatedly).

Did this answer your question?