# Supported Chains and Currencies {% hint style="info" %} **Reach out** For more details on how to start accepting crypto payments, [get in touch](https://2deywy.share-eu1.hsforms.com/2b92phs9LR_eJdeZoxzmoMA?utm_source=request.network\&utm_medium=docs\&utm_campaign=evergreen\&utm_content=get_in_touch) and we will reach out. {% endhint %} ## Request Network API Supported Chains and Currencies Overall, the Request Network API supports 500+ currencies across 10 EVM chains. ### ERC20, Native, and Conversion Payments Supported Chains 10 EVM Chains: * Ethereum * Arbitrum One * OP Mainnet * Base * Polygon * BSC * Avalanche * Fantom * zkSync Era * Sepolia ### ERC20 and Native Payments Supported Currencies For ERC20 and Native Payments, the Request Network API supports 500+ tokens, mostly on Ethereum. See [Request Network Token List](/general/request-network-token-list.md) for the full list. {% hint style="info" %} The [Request Network Token List](/general/request-network-token-list.md) is a *super set*, which contains some currencies on non-supported chains. Cross-reference with the [#request-network-api-supported-chains](#request-network-api-supported-chains "mention") {% endhint %} ### Conversion Payments Supported Currencies For Conversion Payments, the Request Network API supports the following *invoice* currencies: * USD * EUR * CNY * GBP * JPY For Conversion Payments, the Request Network API supports the following *payment* currencies: * USDC * USDT * DAI * FAU on Sepolia To get a list of supported *payment* currencies for a given *invoice* currency, use the [#get-v2-currencies-currencyid-conversion-routes](#get-v2-currencies-currencyid-conversion-routes "mention") endpoint. ### Crosschain Payments Supported Currencies See [Crosschain Payments](/request-network-api/crosschain-payments.md#crosschain-payments-supported-chains-and-currencies) ### Crypto-to-fiat Payments Supported Currencies See [Crypto-to-fiat Payments](/request-network-api/crypto-to-fiat-payments.md#crypto-to-fiat-supported-chains-and-currencies) ## Currencies API Endpoint The currencies API endpoints provide access to the complete Request Network token list, enabling you to discover and filter available tokens across multiple blockchain networks. ## Key Features * **Payment Request Integration**: Get the exact currency IDs needed for creating payment requests * **Payment Integration**: Get accurate token information for payment processing * **Currency Validation**: Verify supported tokens before creating payment requests * **Multi-Chain Support**: Access tokens across Ethereum, Polygon, Arbitrum, and more * **Developer-Friendly**: Simple filtering options for easy integration ## Currency Information Structure Each token in the response includes: * **id**: Unique Request Network token identifier (e.g., `USDC-mainnet`) * **name**: Human-readable token name (e.g., `USD Coin`) * **symbol**: Token symbol (e.g., `USDC`) * **decimals**: Number of decimal places for the token * **address**: Contract address on the specified network * **network**: Blockchain network name * **type**: Token type (`ERC20`, `ETH`, etc.) * **hash**: Contract address hash * **chainId**: Blockchain chain ID ## Endpoints ## Get currencies > Get a list of all available tokens, or filter by network, symbol, or id. ```json {"openapi":"3.0.0","info":{"title":"Request Network API","version":"0.18.3"},"tags":[{"name":"V2/Currencies","description":"Currency operations (V2)"}],"servers":[{"url":"https://api.request.network","description":"Production server"},{"url":"https://api.stage.request.network","description":"Staging server"},{"url":"http://127.0.0.1:8080","description":"Local development server"}],"paths":{"/v2/currencies":{"get":{"description":"Get a list of all available tokens, or filter by network, symbol, or id.","operationId":"CurrenciesV2Controller_getNetworkTokens_v2","parameters":[{"name":"x-api-key","in":"header","description":"API key for authentication (optional if using Client ID or session)","required":false,"schema":{"type":"string"}},{"name":"x-client-id","in":"header","description":"Client ID for frontend authentication (optional if using API key or session)","required":false,"schema":{"type":"string"}},{"name":"Origin","in":"header","description":"Origin header (required for Client ID auth, automatically set by browser)","required":false,"schema":{"type":"string"}},{"name":"network","required":false,"in":"query","description":"The network of the token(s)","schema":{"type":"string"}},{"name":"symbol","required":false,"in":"query","description":"The symbol of the token","schema":{"type":"string"}},{"name":"firstOnly","required":false,"in":"query","description":"Whether to return only the first token. can only be used when both `network` and `symbol` are provided.","schema":{"type":"string"}},{"name":"id","required":false,"in":"query","description":"The Request Network id of the token","schema":{"type":"string"}}],"responses":{"200":{"description":"List of tokens retrieved successfully","content":{"application/json":{}}},"400":{"description":"Validation failed","content":{"application/json":{}}},"404":{"description":"Token not found","content":{"application/json":{}}},"429":{"description":"Too Many Requests"}},"summary":"Get currencies","tags":["Currencies","V2/Currencies"]}}}} ``` ## Get conversion routes for a specific currency > Get a list of currency objects (with all details) that can be converted to from the specified currency. Optionally filter by network using the 'network' query parameter. ```json {"openapi":"3.0.0","info":{"title":"Request Network API","version":"0.18.3"},"tags":[{"name":"V1/Currencies","description":"Currency operations (V1)"}],"servers":[{"url":"https://api.request.network","description":"Production server"},{"url":"https://api.stage.request.network","description":"Staging server"},{"url":"http://127.0.0.1:8080","description":"Local development server"}],"paths":{"/v1/currencies/{currencyId}/conversion-routes":{"get":{"description":"Get a list of currency objects (with all details) that can be converted to from the specified currency. Optionally filter by network using the 'network' query parameter.","operationId":"CurrenciesV1Controller_getConversionRoutes_v1","parameters":[{"name":"currencyId","required":true,"in":"path","schema":{"type":"string"}},{"name":"x-api-key","in":"header","description":"API key for authentication (optional if using Client ID or session)","required":false,"schema":{"type":"string"}},{"name":"x-client-id","in":"header","description":"Client ID for frontend authentication (optional if using API key or session)","required":false,"schema":{"type":"string"}},{"name":"Origin","in":"header","description":"Origin header (required for Client ID auth, automatically set by browser)","required":false,"schema":{"type":"string"}},{"name":"network","required":false,"in":"query","description":"The network of the token to filter by","schema":{"type":"string"}},{"name":"networks","required":false,"in":"query","description":"A comma-separated list of networks to filter by (e.g., sepolia,mainnet,polygon)","schema":{"type":"string"}}],"responses":{"200":{"description":"Conversion routes retrieved successfully","content":{"application/json":{}}},"404":{"description":"Currency not found","content":{"application/json":{}}},"429":{"description":"Too Many Requests"}},"summary":"Get conversion routes for a specific currency","tags":["Currencies","V1/Currencies"]}}}} ``` --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://legacy.docs.request.network/request-network-api/supported-chains-and-currencies.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.