Airwallex · Rate Limits

Airwallex Rate Limits

Published Airwallex API rate and concurrency limits. Airwallex enforces two distinct controls - a rate limit (requests over a rolling window) and a concurrency limit (in-flight requests) - at three levels: global (all endpoints for an account/org), endpoint (one operation across all resources), and resource (one specific resource id). The authentication endpoint is carved out with its own fixed limit.

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

It captures 8 rate-limit definitions, measuring requests_per_second, concurrent_requests, and requests_per_minute.

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

Tagged areas include Cross-Border Payments, FinTech, Payments, Rate Limiting, and Throttling.

8 Limits Throttle: 429 Quota: 429
Cross-Border PaymentsFinTechPaymentsRate LimitingThrottling

Limits

Production global rate limit account-or-organization
requests_per_second · second
100
Production per-endpoint rate limit endpoint
requests_per_second · second
20
Production global concurrency limit account-or-organization
concurrent_requests
50
Sandbox global rate limit account-or-organization
requests_per_second · second
20
Sandbox per-endpoint rate limit endpoint
requests_per_second · second
10
Sandbox global concurrency limit account-or-organization
concurrent_requests
10
Authentication endpoint limit api-key
requests_per_minute · minute
100
Resource-level limits resource
requests_per_second

Policies

Backoff strategy
On a 429, retry with exponential backoff plus random jitter - 1s, 2s, 4s, doubling to a ceiling of roughly 16s. Jitter is explicitly called for so clients do not synchronize retries.
Client-side throttling
For scheduled batch tasks and high-volume operations, implement client-side throttling to stay within the account and endpoint limits rather than relying on 429s.
Uplift
Higher production limits, including temporary uplifts for events such as a flash sale, are arranged through Airwallex support rather than self-serve.
Load testing
Airwallex discourages load testing in the sandbox - its lower limits and mock mechanisms produce misleading results. It recommends mocking the Airwallex API with production-measured latency instead.

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/airwallex-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.