OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Airwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting.
Account balances and Wallet balance movements have structured GET interfaces.
Balances and balance history ↗
List all Current Balances; Retrieve the Balance History · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Airwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting.
Bookmark pagination traverses the permitted Wallet history; page_size is 10–2000.
Balances and balance history ↗
Retrieve the Balance History > page; page_size; page_after · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Airwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting.
Filter currency, account type, request ID and posted-time range.
Balances and balance history ↗
Retrieve the Balance History > Query parameters · Checked 2026-10-16
Access cost barrier -
-
Airwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting.
The lowest eligible paid plan and route-specific fixed API charges have not been established.
Manage API keys ↗
Manage API keys; Create an access token using a scoped API key · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 5.0/10
Separate provider consent or partner agreement required
Airwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting.
Multi-customer OAuth application credentials require the partner team and pre-authorized scopes.
Partner connections: Get started ↗
Request authentication credentials; Determine scopes and permissions · Checked 2026-10-16
Downstream permission -
-
Airwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting.
Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation.
Manage API keys ↗
Manage API keys; Create an access token using a scoped API key · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface -
-
Airwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting.
The reviewed route does not establish a named business-record mutation; write capability remains unknown.
Manage API keys ↗
Manage API keys; Create an access token using a scoped API key · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Airwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting.
Customers can configure their own scoped integration keys; partner distribution is separate.
Manage API keys ↗
Manage API keys; Scoped API keys · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism -
-
Airwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting.
Posted-time windows select balance activity, but updated-since discovery, provider-scheduled delivery and webhook refresh are not established for this read scope.
Balances and balance history ↗
Retrieve the Balance History > from_post_at; to_post_at · Checked 2026-10-16
Limit visibility -
-
Airwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting.
Numeric page size is documented, but request-rate quotas and recovery timing are not established here.
Balances and balance history ↗
Retrieve the Balance History > page_size; Errors · Checked 2026-10-16
CDC and deletion capture 2.5/10
Full snapshots permit customer reconciliation; native deltas unverified
Airwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting.
Repeat permitted balance-history pages for customer reconciliation. Complete updated-record and deletion identities remain unestablished.
Balances and balance history ↗
Retrieve the Balance History > page; page_after; Response body · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Airwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting.
Repeat complete permitted Wallet history with page=0 and follow bookmarks. No intermediate versions, deleted payloads or retained event-checkpoint contract is established.
Balances and balance history ↗
Retrieve the Balance History > page; page_after; page_before · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Airwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting.
Structured balance movements can be retained by the caller.
Balances and balance history ↗
Retrieve the Balance History > Response body · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Airwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting.
A customer cancellation retrieval window and any exit charges have not been established.
Manage API keys ↗
Manage API keys; Create an access token using a scoped API key · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Airwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting.
Portable balance records are documented; other Airwallex product records and configuration are outside scope.
Balances and balance history ↗
Retrieve the Balance History > Response body · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Airwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting.
External account-scoped reporting code is supported; native logic portability remains unresolved.
Manage API keys ↗
Manage API keys · Checked 2026-10-16
Rights to custom logic -
-
Airwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting.
Ownership, reusable export and independent execution of native workflow definitions remain unresolved.
Manage API keys ↗
Manage API keys; Create an access token using a scoped API key · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
Owner, Admin or Developer roles manage customer API keys. A scoped key plus client ID yields a 30-minute token; a key linked to several accounts needs x-login-as for account access, while partner OAuth applications request their own credentials and listing.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
GET /api/v1/balances/current returns available and pending currency balances. GET /api/v1/balances/history supports currency, account type and posted-time windows, with page_after/page_before bookmarks; page=0 bypasses the default seven-day window for a complete Wallet-record search.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Airwallex customer API | API key | Customer | Not confirmed | Customer-supplied credentials | 2026-10-16 |
| Airwallex partner OAuth application | OAuth 2.0 | Integration provider | Yes | Partner approval | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
The lowest eligible customer plan and any fixed API, partner or setup charges remain unestablished. Payment-processing charges do not by themselves establish an API-access surcharge.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
The assessed balance endpoints retrieve data. No payment creation, payout or balance adjustment operation is established by this reporting scope; such actions need their own API permission and approval contract.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Posted-time windows allow repeated overlapping balance-history extraction, and bookmarks paginate returned records. The documented seven-day constraint applies to page_num date windows, not a stated history-retention limit; update/deletion signals and durable event replay remain unresolved.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Full snapshots permit customer reconciliation; native deltas unverifiedAirwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting. Repeat permitted balance-history pages for customer reconciliation. Complete updated-record and deletion identities remain unestablished. | Balances and balance history ↗Retrieve the Balance History > page; page_after; Response bodyChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedAirwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting. Repeat complete permitted Wallet history with page=0 and follow bookmarks. No intermediate versions, deleted payloads or retained event-checkpoint contract is established. | Balances and balance history ↗Retrieve the Balance History > page; page_after; page_beforeChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Customers can retain structured balances and balance movements outside Airwallex. These records support reconciliation, but do not establish all payment attachments, compliance records or organization configuration needed for whole-product migration.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customer-authored integration code can reconcile balances and apply external reporting rules (with account selection enforced by the key). Native workflow ownership and independent execution remain unestablished.
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeAirwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting. Account balances and Wallet balance movements have structured GET interfaces. | Balances and balance history ↗List all Current Balances; Retrieve the Balance HistoryChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsAirwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting. Bookmark pagination traverses the permitted Wallet history; page_size is 10–2000. | Balances and balance history ↗Retrieve the Balance History > page; page_size; page_afterChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersAirwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting. Filter currency, account type, request ID and posted-time range. | Balances and balance history ↗Retrieve the Balance History > Query parametersChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Separate provider consent or partner agreement requiredAirwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting. Multi-customer OAuth application credentials require the partner team and pre-authorized scopes. | Partner connections: Get started ↗Request authentication credentials; Determine scopes and permissionsChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Airwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting. The lowest eligible paid plan and route-specific fixed API charges have not been established. | Manage API keys ↗Manage API keys; Create an access token using a scoped API keyChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Airwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting. Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation. | Manage API keys ↗Manage API keys; Create an access token using a scoped API keyChecked 2026-10-16 |
| Which external write operations are documented? | -Airwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting. The reviewed route does not establish a named business-record mutation; write capability remains unknown. | Manage API keys ↗Manage API keys; Create an access token using a scoped API keyChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionAirwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting. Customers can configure their own scoped integration keys; partner distribution is separate. | Manage API keys ↗Manage API keys; Scoped API keysChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | -Airwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting. Posted-time windows select balance activity, but updated-since discovery, provider-scheduled delivery and webhook refresh are not established for this read scope. | Balances and balance history ↗Retrieve the Balance History > from_post_at; to_post_atChecked 2026-10-16 |
| How are integration limits disclosed? | -Airwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting. Numeric page size is documented, but request-rate quotas and recovery timing are not established here. | Balances and balance history ↗Retrieve the Balance History > page_size; ErrorsChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsAirwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting. Structured balance movements can be retained by the caller. | Balances and balance history ↗Retrieve the Balance History > Response bodyChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Airwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting. A customer cancellation retrieval window and any exit charges have not been established. | Manage API keys ↗Manage API keys; Create an access token using a scoped API keyChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedAirwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting. External account-scoped reporting code is supported; native logic portability remains unresolved. | Manage API keys ↗Manage API keysChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Airwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting. Ownership, reusable export and independent execution of native workflow definitions remain unresolved. | Manage API keys ↗Manage API keys; Create an access token using a scoped API keyChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedAirwallex account-scoped balances and Wallet balance history API; organization-level keys and partner OAuth are separate grants, and no payment-mutation surface is inferred from reporting. Portable balance records are documented; other Airwallex product records and configuration are outside scope. | Balances and balance history ↗Retrieve the Balance History > Response bodyChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- The lowest eligible paid plan and route-specific fixed API charges have not been established.
- Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation.
- The reviewed route does not establish a named business-record mutation; write capability remains unknown.
- Posted-time windows select balance activity, but updated-since discovery, provider-scheduled delivery and webhook refresh are not established for this read scope.
- Numeric page size is documented, but request-rate quotas and recovery timing are not established here.
- A customer cancellation retrieval window and any exit charges have not been established.
- Ownership, reusable export and independent execution of native workflow definitions remain unresolved.
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.