v3 is in preview. If you’re starting a new integration, consider migrating to v3 — v3 introduces stable error codes, bare-resource responses, and a
/v3/fx/ surface.v2 is the current generation of the OpenFX API. If you are integrating from v1, see the migration guide for the breaking changes (most notably required
Idempotency-Key headers on POST endpoints).Why OpenFX?
Financial institutions benefit from:- Access to multiple currency pairs on a single platform at institutional exchange rates
- Trading without the need to pre-fund accounts on the platform
- Same-day (T0) settlement into web3 wallets and bank accounts globally
- 24/7 conversion availability with always-on liquidity and support
Who we serve
OpenFX APIs are used by financial services institutions and fintechs across the following segments.Remittance firms
- Capture margin improvement through institutional FX rates that beat traditional banking spreads.
- Improve balance-sheet efficiency by compressing settlement cycles to same-day execution.
- Activate new corridors without capital-intensive pre-funding.
Neobanks
- Offer customers FX conversion rates backed by institutional liquidity.
- Simplify global treasury operations with multi-currency holdings and conversions.
- Equip trade-operations teams with intelligent routing, cash management, and liquidity control.
Payment processors
- Reduce payment processing costs by leveraging stablecoin infrastructure and local-currency settlement.
- Move funds 24/7 across weekends, holidays, and non-banking hours.
- Deliver near-instant global payment experiences.
Neo-brokers
- Access stablecoin-to-fiat exchange rates through direct connectivity with stablecoin issuers.
- Eliminate unnecessary conversion steps by tapping local fiat-stablecoin liquidity channels.
- Manage liquidity across 9+ blockchain networks without per-chain complexity.
Global payroll companies
- Distribute payroll at competitive FX rates, lowering transaction costs.
- Settle payroll via stablecoin and fiat rails for improved reliability.
- Reduce operational overhead by removing global pre-funding requirements.
Next steps
Authenticate
Generate an ES256-signed JWT bearer token to call any v2 endpoint.
Browse the API
See every v2 endpoint grouped by domain.
Test in Sandbox
Validate your integration against the isolated Sandbox environment before going live.