The Super Payments API uses a number of safeguards against bursts of incoming traffic to help maximise its stability. Treat these limits as maximums and don’t generate unnecessary load. Users who send many requests in quick succession might see error responses that show up as status code 429. We have several limiters in the API, including:

A rate limiter that limits the number of requests received by the API within any given second.

For most APIs, We allow up to 20 read operations per second and 20 write operations per second.

A concurrency limiter that limits the number of requests that are active at any given time. Problems with this limiter are less common compared to the request rate limiter, but it’s more likely to result in resource-intensive, long-lived requests.

We may reduce limits to prevent abuse, or increase limits to enable high-traffic applications.