Rate limiting

Moov implements rate limiting for security and performance optimization. Use this guide to learn how Moov uses rate limiting.

By limiting the number of requests hitting our API, we can manage request volume at scale, keeping Moov’s platform reliable for the many developers and platforms interacting with our services.

How we use rate limits

We currently limit the number of requests by any given IP address to 40 requests per second per account ID. If you exceed the request limit for our API, all endpoints will respond with a 429 status code, indicating you have made too many requests.

Test accounts are limited to 10 requests per second per account ID.

What to do when you get a 429 response

The 429 response header will note how much time you have until you can retry the request.

How to increase rate limits

If you need to increase your rate limit for your account, contact us with details about your use case and we’re happy to raise the limit.

Summary Beta