Skip to main content

Rate and Request Limiting

We use safeguards against bursts of incoming traffic and excessive request sizes to maximize API stability. If you send many requests in quick succession, you might receive 429 error responses. If you send a request that exceeds our request size limits, you will receive a 413 error response.

Rate Limits​

The Partner API limits requests to 500 per 5 minutes per IP address. Treat limits as maximums and avoid unnecessary load. To prevent abuse, we may reduce limits for accounts with unusual traffic patterns.

Handling Rate Limits​

If you receive a 429 error:

  • Implement exponential backoff - Wait progressively longer between retries (1s, 2s, 4s, etc.)
  • Spread out requests - Use queuing mechanisms and distribute bulk operations over time
  • Cache responses - Reduce redundant API calls for data that doesn't change frequently
  • Monitor usage - Track request volumes and set up alerts for unusual spikes

Requesting a Limit Increase​

For high-traffic applications, contact your Paytient account manager or email support at support@paytient.com with details about your use case.

Request Limits​

The Partner API enforces a max request payload size of 10 MB. Additionally, the combined size of all HTTP headers, URL parameters, and the request line cannot exceed 10 KB.

Handling Request Limits​

If you receive a 413 error:

  • Implement compression - The most frequent cause of 413 errors is uncompressed images when uploading documents. Compressing images prior to upload can significantly reduce payload size.
  • Verify headers - Avoid passing large tokens or arrays in headers or query strings