Xendit · Rate Limits

Xendit Rate Limits

Xendit applies default per-endpoint, per-account request-rate limits that differ by environment. Test mode is limited to 60 requests per minute (RPM) per endpoint per account, and live mode to 600 RPM per endpoint per account. A separate per-IP ceiling of 18,000 requests per minute applies across each unique source IP. Some endpoints publish their own limits in their API reference section that override these defaults. When a limit is exceeded the API returns HTTP 429 with the error code RATE_LIMIT_EXCEEDED.

Xendit Rate Limits is the machine-readable rate-limit profile for Xendit on the APIs.io network, in the API Commons Rate Limits shape.

It captures 4 rate-limit definitions, measuring requests.

Limit state is signalled in the Rate-Limit-Limit, Rate-Limit-Remaining, and Rate-Limit-Reset response headers, and an exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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

Tagged areas include Payments, Fintech, Southeast Asia, Rate Limiting, and Quotas.

4 Limits Exhausted: HTTP 429 Rate-Limit-LimitRate-Limit-RemainingRate-Limit-Reset
Method: generated, dated 2026-07-12.
Written by API Evangelist on 2026-07-12 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
PaymentsFintechSoutheast AsiaRate LimitingQuotas

Limits

Test Mode Requests endpoint-per-account
requests
60 per minute
Default test-mode ceiling per endpoint per account.
Live Mode Requests endpoint-per-account
requests
600 per minute
Default live-mode ceiling per endpoint per account.
Per-IP Requests ip
requests
18000 per minute
Applies to each unique source IP address across endpoints.
Per-Endpoint Overrides endpoint
requests
varies
Some endpoints publish their own limit in their API reference section.

Policies

Throttling Response
Exceeding a limit returns HTTP 429 with error code RATE_LIMIT_EXCEEDED.
Backoff Strategy
Clients should honor the Rate-Limit-Reset header and apply exponential backoff with jitter on 429 responses.
Idempotency
Money-moving endpoints (e.g. payouts) accept an Idempotency-key header so retried requests do not create duplicates.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/xendit-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.