GET /currencies/supported to discover which source-to-destination currency routes are available for your project.
Request
Response
from— source currency codeto— destination currency codeproviderIds— IDs of providers that can handle this route (at theProvider.idlevel)
GET /providers with Basic Auth. These provider IDs appear in two places later in the flow:
- Requirements — when you call
GET /external-accounts/requirements, the response may include provider-specific fields viadependenciesin the JSON Schema. - Intent creation — you can pass a
providerIdtoPOST /intentto pin a specific provider. This must be one of theproviderIdsfrom this response for the relevant currency pair.
Currency Code Format
| Type | Format | Examples |
|---|---|---|
| Fiat | Standard ISO 4217 | USD, EUR, BRL, ARS |
| Crypto | {ticker}_{blockchain} | USDC_ETH, USDC_GNO, USDC_BASE |
Using the Response
Use the supported currencies list to:- Build currency selectors — only show users the currency pairs your project supports.
- Pass
src/destto requirements — use thefrom/tovalues when callingGET /external-accounts/requirements. - Validate before account creation — ensure the currency pair is supported before creating external accounts.
- Show available providers — use
providerIdsto let users pick a preferred provider, or let GnosisRamp auto-select.