Rate limits
The API may apply rate limits to incoming requests to protect service availability and ensure fair usage. Each endpoint has its own limits and can be applied by merchant or globally. The specific limits are not published and may vary by endpoint and throughout time.
If a limit is reached, the API responds with 429 Too Many Requests. When
available, the response also may include a Retry-After header indicating
how long to wait before retrying the request. For details,
see the HTTP status codes.
Tips to avoid being rate-limited
- Use webhooks instead of polling.
- Distribute requests over time rather than sending them in parallel.
- Limit the number of concurrent workers making requests to our API.
If you expect a traffic spike or a high-volume event, contact Nomupay's support team in advance to discuss your requirements.