An API reference is the contract between your code and Airwallex systems. It lists resources, HTTP methods, parameters, response fields, and error shapes.
Expect separate resource groups for payments, customers/payment methods, transfers/beneficiaries, FX quotes/conversions, accounts, and issuing cards—depending on what your programme enables.
References answer “what fields exist?” while guides answer “in what order should I call them?”. Production teams need both.
Versioning and deprecation notices in the reference matter for long-lived integrations; pin versions thoughtfully.
Use the reference together with sandbox traffic inspection so real payloads match documented schemas.
Key points
- Resource-level contracts for requests and responses
- Covers payments, accounts, FX, payouts, and issuing areas
- Complement—not replace—workflow guides and examples
- Watch versioning and deprecation for stable integrations
Informational page about Airwallex. Availability, fees, and features can vary by region and plan.