Appearance
Rate Limits
TiruPay enforces rate limits on its API endpoints to keep the service stable and to protect against abusive or runaway clients. If you send too many requests to a given endpoint in a short period, TiruPay rejects the extra requests with an HTTP 429 Too Many Requests response instead of processing them.
How Limits Are Scoped
Each endpoint has its own independent limit. Calling one endpoint a lot does not affect your allowance on another endpoint.
Within an endpoint, the limit is tracked per caller:
- If your request carries a valid
Authorization: Bearertoken, the limit is scoped to that authenticated user. - Otherwise, it falls back to the client's IP address.
Service accounts get more headroom
Endpoints that accept both Admin and Service calls apply a higher default allowance to Service-authenticated requests than to Admin requests. A handful of especially sensitive endpoints (for example initiating a withdrawal, or sending a manual email) use their own, stricter, custom limit regardless of caller type.
Exceeding the Limit
Once you go over an endpoint's limit, further requests to it get:
http
HTTP/1.1 429 Too Many Requests
{
"detail": "Too many requests. Try again in <seconds> seconds."
}The number of seconds tells you how long until your allowance resets - wait at least that long before retrying. Retrying immediately just extends how long you stay rate limited.
Build retry logic around this
If your integration calls an endpoint in a loop or in response to bursts of user activity, handle 429 explicitly: back off and retry after the indicated delay rather than failing the whole operation.
Good to Know
OPTIONS and HEAD are never limited
Preflight and metadata requests don't count against any endpoint's limit.
Relationships
- Idempotency Keys - Use idempotency keys instead of blind retries to avoid burning through your rate limit allowance on repeated attempts of the same operation.