What are the SekaliPay API rate limits?

Limits are counted per API key, per endpoint, per minute: 5 for creating payments, 2 for withdrawals, 30 for status checks, and 60 for the other read endpoints. Going over returns 429 RATE_LIMIT_EXCEEDED with a Retry-After header.

This page was checked against the API code as of October 16, 2026.

What is the limit for each endpoint?#

Method	Path	Purpose	Limit per minute	Signature
POST	/payment	Create payment	5	Required in both modes
GET	/payment/{merchant_ref_id}	Payment status	30	Enhanced HMAC only
GET	/payment-methods	Payment methods	60	Enhanced HMAC only
GET	/merchant/info	Account info	60	Enhanced HMAC only
POST	/withdrawal	Withdrawals	2	Required in both modes

Limits are the same in IP Whitelist and Enhanced HMAC mode. Status checks share one counter across all merchant_ref_id values, not one per ref.

What happens when I exceed a limit?#

429 Too Many Requests

{
  "success": false,
  "message": "Too many requests. Please try again later.",
  "retry_after": 42,
  "error_code": "RATE_LIMIT_EXCEEDED"
}

Wait retry_after seconds (the same as the Retry-After header) before trying again.

The X-RateLimit-Limit and X-RateLimit-Remaining response headers currently show the general limit, not each endpoint's effective limit. Rely on the table above and on 429 responses.

How do I stay under the limits?#

Rely on webhooks for status, not polling.
Cache the method list instead of fetching it per buyer.
During order spikes, queue payment creation on your server and send at most 5 per minute per API key.
Need more than that? Contact us to discuss your needs.

Ready to use your own keys?

Sign in to the merchant dashboard to copy your API key and secret key, set the access mode and webhook URL, and download a Postman collection with your account's keys.