Digio · Rate Limits

Digio Rate Limits

Digio does not publish specific numeric API rate limits in its public documentation. Throughput is governed by the negotiated enterprise contract and by underlying regulated rails (UIDAI for Aadhaar, NPCI for eNACH/NACH), each of which imposes its own transaction ceilings. Clients should implement retries with backoff and rely on webhook callbacks for asynchronous status rather than tight polling.

Digio Rate Limits is the machine-readable rate-limit profile for Digio on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests, transactions, and mandates.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include eSign, KYC, eNACH, India, and Rate Limiting.

3 Limits Throttle: 429
eSignKYCeNACHIndiaRate LimitingQuotas

Limits

Account throughput account
requests
see contract / not publicly documented
Governed by the enterprise agreement.
Aadhaar eKYC / eSign regulated-rail
transactions
subject to UIDAI limits
Aadhaar-based flows are bounded by UIDAI ceilings and per-transaction fees.
eNACH / NACH regulated-rail
mandates
subject to NPCI limits
Mandate registration and debit throughput follow NPCI NACH rules.

Policies

Backoff Strategy
Use exponential backoff with jitter on 429/5xx and honor Retry-After.
Webhook-first
Register webhook callbacks for status changes instead of aggressive polling of GET status endpoints.

Sources