DOKU · Rate Limits

Doku Rate Limits

DOKU does not publish explicit numeric per-endpoint rate limits in its public developer documentation. Practical throughput controls come from the Bank Indonesia SNAP framework: the B2B access token is valid for 15 minutes and must be reused (not re-minted per call), each transaction carries a unique X-EXTERNAL-ID enforcing idempotency/duplicate rejection, and merchant accounts are subject to fraud/velocity and settlement controls set in the DOKU Back Office. Specific RPS/RPM ceilings are governed by the merchant agreement and are not documented publicly.

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

It captures 3 rate-limit definitions, measuring token_lifetime, unique_identifier, and requests.

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

Tagged areas include Payments, Payment Gateway, Indonesia, Rate Limiting, and Quotas.

3 Limits Throttle: 429
PaymentsPayment GatewayIndonesiaRate LimitingQuotasSNAP

Limits

SNAP Access Token TTL account
token_lifetime
900 seconds
B2B Bearer token valid 15 minutes; reuse until expiry rather than minting per request.
Idempotency (X-EXTERNAL-ID) request
unique_identifier
unique per transaction per day
SNAP rejects duplicate X-EXTERNAL-ID values; used for de-duplication, not a rate ceiling.
Per-endpoint request rate account
requests
see merchant agreement
No public numeric RPS/RPM published; governed contractually and by fraud/velocity controls.

Policies

Token Reuse
Cache and reuse the SNAP B2B access token for its 15-minute lifetime instead of requesting a new token per call.
Backoff Strategy
On HTTP 429 or 5xx, retry with exponential backoff and jitter; never replay a successful payment with a new X-EXTERNAL-ID.
Idempotency
Generate a unique X-EXTERNAL-ID / partnerReferenceNo per logical transaction to guarantee exactly-once processing.

Sources