> ## Documentation Index > Fetch the complete documentation index at: https://docs.meshconnect.com/llms.txt > Use this file to discover all available pages before exploring further. # Get networks > **Get supported networks list.** --- Get the list of all networks supported by Mesh to perform transfers, including which tokens and integrations are supported. The response always includes validation data: - `addressPattern`: The regex pattern for validating addresses on this network - `contractAddress`: For each token, the contract address (if applicable) to enable ERC20 contract address validation ## OpenAPI ````yaml get /api/v1/transfers/managed/networks openapi: 3.0.1 info: title: Mesh Connect Integration API description: >- Mesh allows users to connect accounts of financial institutions, crypto exchanges, and self-custody wallets. Mesh handles credential validation, MFA, and error handling for each integration. After an account is connected, Mesh allows client applications to read holdings, transaction history and balances and execute crypto transfers (with user approval). version: '1.0' servers: - url: https://integration-api.meshconnect.com - url: https://sandbox-integration-api.meshconnect.com security: - Client-Secret: [] Client-Id: [] tags: - name: BlockchainQuery - name: Integrations account information - name: Managed Account Authentication description: >- The recommended approach for account authentication. Front manages multiple authentication flows and handles all authentication steps such as MFA codes and OAuth redirect through our web and mobile SDKs. - name: Portfolio description: | ### Supported integrations: ```Robinhood``` ```Coinbase``` ```Kraken``` ```CryptoCom``` ```OpenSea``` ```Binance``` ```Gemini``` ```OkCoin``` ```KuCoin``` ```CexIo``` ```BinanceInternational``` ```Bitstamp``` ```GateIo``` ```Okx``` ```BitFlyer``` ```Coinlist``` ```Huobi``` ```Bitfinex``` ```KrakenDirect``` ```BinanceInternationalDirect``` ```BitfinexDirect``` ```Bybit``` ```Paxos``` ```CoinbasePrime``` ```BtcTurkDirect``` ```KuCoinDirect``` ```OkxOAuth``` ```ParibuDirect``` ```RobinhoodConnect``` ```BlockchainCom``` ```BitsoDirect``` ```BinanceOAuth``` ```BybitDirect``` ```ParibuOAuth``` ```BinanceTrDirect``` ```BybitDirectMobile``` ```Sandbox``` ```Uphold``` ```SandboxCoinbase``` ```BluvoKrakenOAuth``` ```DeFiWallet``` - name: Balance description: | ### Supported integrations: ```Robinhood``` ```Coinbase``` ```Kraken``` ```CryptoCom``` ```Binance``` ```Gemini``` ```OkCoin``` ```KuCoin``` ```CexIo``` ```BinanceInternational``` ```Bitstamp``` ```GateIo``` ```Okx``` ```BitFlyer``` ```Coinlist``` ```Huobi``` ```Bitfinex``` ```KrakenDirect``` ```BinanceInternationalDirect``` ```BitfinexDirect``` ```Bybit``` ```Paxos``` ```CoinbasePrime``` ```BtcTurkDirect``` ```KuCoinDirect``` ```OkxOAuth``` ```ParibuDirect``` ```RobinhoodConnect``` ```BlockchainCom``` ```BitsoDirect``` ```BybitDirect``` ```ParibuOAuth``` ```BinanceTrDirect``` ```BybitDirectMobile``` ```Sandbox``` ```Uphold``` ```SandboxCoinbase``` ```BluvoKrakenOAuth``` - name: Transfers description: > ### Supported integrations: ```Robinhood``` ```Coinbase``` ```Kraken``` ```CryptoCom``` ```Binance``` ```Gemini``` ```OkCoin``` ```KuCoin``` ```BinanceInternational``` ```Bitstamp``` ```GateIo``` ```Okx``` ```Huobi``` ```Bitfinex``` ```KrakenDirect``` ```BinanceInternationalDirect``` ```BitfinexDirect``` ```Bybit``` ```Paxos``` ```CoinbasePrime``` ```BtcTurkDirect``` ```ParibuDirect``` ```RobinhoodConnect``` ```BlockchainCom``` ```BinanceConnect``` ```RevolutConnect``` ```BinancePay``` ```BybitDirect``` ```ParibuOAuth``` ```PayPalConnect``` ```CoinbaseRamp``` ```BybitDirectMobile``` ```Sandbox``` ```CryptoComPay``` ```Uphold``` ```BinancePayOnchain``` ```SandboxCoinbase``` ```BybitPay``` ```DeFiWallet``` ### Integration-specific notes: #### Robinhood: Cryptocurrency transfers should be enabled in Robinhood settings. Transfers are disabled by default, enabling them for end users requires a review from Robinhood. Please note: * `MfaCode` parameter is required to initiate a transaction in Robinhood. * The user's security settings should be configured to use an authenticator application. * Robinhood doesn't allow initiation of transactions if the authenticator application is not configured. #### Coinbase: `MfaCode` parameter should be used to initiate transactions in Coinbase. * If the end user's Coinbase account is configured to use text messages (SMS) for two factor authentication, the API will return `MfaRequired` status, and a text code will then be sent by Coinbase. The code is expected to be provided in the subsequent call using the `MfaCode` request field * If the account is configured to use an authenticator application, the API is expecting to get the code in the `MfaCode` request field. #### Kraken: Kraken requires the explicit chain name to be provided (e.g. `Dogecoin` or `Ethereum (ERC20)`). The list of possible chains can be obtained by calling `symbol/details` endpoint. To initiate a transaction, a Kraken Address Key name should be provided in `TargetAddress` field. Target address should be added using Kraken UI, then its name should be used. #### Binance: `Enable Withdrawals` permission should be given to the user's API key to initiate transfers with Binance Us. Binance requires adding the IP address to the list of trusted IPs to be able to create API keys with transfer permission. * Please reach out to Front to get the static IP address. This address should be provided to the end user, and the user should be instructed to add it to the list of trusted IP addresses. * By default, the permission to enable withdrawals is turned off. If the end user's API key does not have the permission, asset transfers will not be available. #### KuCoin: KuCoin requires adding the IP address to the list of trusted IPs to be able to create API keys with transfer permission. `Fee` parameter should be used to initiate a transaction in KuCoin. Please note: * Please reach out to Front to get the static IP address. This address should be provided to the end user, and the user should be instructed to add it to the list of trusted IP addresses. * All currencies have their minimum `fee` and `amount` requirements. Please use `symbol/details` endpoint to get this data for a particular symbol. * KuCoin requires chain name to be provided for getting deposit address or initiating a cryptocurrency transfer. Some cryptocurrencies are supported over multiple chains. It's recommended to use `symbol/details` endpoint to get the list of supported chains and show it to the end user to select a target one. #### BinanceInternational: `Enable Withdrawals` permission should be given to the user's API key to initiate transfers with Binance International. Binance requires adding the IP address to the list of trusted IPs to be able to create API keys with transfer permission. * Please reach out to Front to get the static IP address. This address should be provided to the end user, and the user should be instructed to add it to the list of trusted IP addresses. * By default, the permission to enable withdrawals is turned off. If the end user's API key does not have the permission, asset transfers will not be available. #### GateIo: Gate.io requires adding IP address to the list of trusted IP addresses to be able to initiate a cryptocurrency transfers. Withdrawal address should be already verified or added on the Gate.io UI (in mobile application or on the web site). * Please reach out to Front to get the static IP address for withdrawals. This address should be provided to the end user, and the user should be instructed to add it to the list of trusted IP addresses. * Only verified withdrawal blockchain addresses are allowed for withdrawal with Gate.io API. * Gate.io requires chain name to be provided for getting deposit address or initiating a cryptocurrency transfer. Some cryptocurrencies are supported over multiple chains. It's recommended to use `symbol/details` endpoint to get the list of supported chains and show it to the end user to select a target one. #### Huobi: Warning: Huobi does not refund executed deposits that are below the `Minimum Deposit Amount` * Please check the MinimumDepositAmount in Get Deposit Address response in order to avoid making a deposit below the minimum amount * Huobi does not allow withdrawals to addresses that are not white-listed, please add the address that you would like to withdraw to the white list of addresses through the UI so that a withrawal can be processed #### Bitfinex: * The hash of transfer is not available when making a transfer in Bitfinex. To get the hash please re-query the transfer using the transaction id. * Bitfinex does not separate sub-accounts when returning the list of transfers.Therefore the same list of transfers is returned for all Bitfinex sub-accounts. #### KrakenDirect: Kraken requires the explicit chain name to be provided (e.g. `Dogecoin` or `Ethereum (ERC20)`). The list of possible chains can be obtained by calling `symbol/details` endpoint. To initiate a transaction, a Kraken Address Key name should be provided in `TargetAddress` field. Target address should be added using Kraken UI, then its name should be used. #### BitfinexDirect: * The hash of transfer is not available when making a transfer in Bitfinex. To get the hash please re-query the transfer using the transaction id. * Bitfinex does not separate sub-accounts when returning the list of transfers.Therefore the same list of transfers is returned for all Bitfinex sub-accounts. - name: Assets - name: Managed Transfers - name: Wallets paths: /api/v1/transfers/managed/networks: get: tags: - Managed Transfers summary: Get networks description: "**Get supported networks list.**\r\n\n\r\n---\r\nGet the list of all networks supported by Mesh to perform transfers, including which tokens and integrations are supported.\r\n\n\n\r\nThe response always includes validation data:\r\n- `addressPattern`: The regex pattern for validating addresses on this network\r\n- `contractAddress`: For each token, the contract address (if applicable) to enable ERC20 contract address validation" responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/NetworkModelResponseApiResult' example: content: networks: - networkType: evm tokens: - symbol: ETH logoUrl: >- https://file-cdn.meshconnect.com/public/logos/tokens/ETH.svg - symbol: USDC logoUrl: >- https://file-cdn.meshconnect.com/public/logos/tokens/USDC.svg contractAddress: '0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48' - symbol: USDT logoUrl: >- https://file-cdn.meshconnect.com/public/logos/tokens/USDT.svg contractAddress: '0xdAC17F958D2ee523a2206206994597C13D831ec7' supportedBrokerTypes: - deFiWallet - robinhood - coinbase - kraken - binanceInternational - binanceUs addressPattern: ^0x[a-fA-F0-9]{40}$ supportedTokens: - ETH - USDC - USDT nativeSymbol: ETH id: e3c7fdd8-b1fc-4e51-85ae-bb276e075611 name: Ethereum chainId: '1' logoUrl: >- https://file-cdn.meshconnect.com/public/logos/networks/Ethereum.svg status: ok message: '' errorHash: 3904604d teamCode: P4 errorType: '' '401': description: Unauthorized content: application/json: schema: {} components: schemas: NetworkModelResponseApiResult: type: object properties: status: enum: - ok - serverFailure - permissionDenied - badRequest - notFound - conflict - tooManyRequest - locked - unavailableForLegalReasons allOf: - $ref: '#/components/schemas/ApiResultStatus' readOnly: true message: type: string description: A message generated by the API nullable: true displayMessage: type: string description: User-friendly display message that can be presented to the end user nullable: true errorHash: type: string description: >- An error grouping hash from string components and caller information. Used by bugsnag on FE for correct error grouping nullable: true readOnly: true teamCode: type: string description: "Opaque team code for error routing. Resolved from exception origin or caller file path via CODEOWNERS.\r\nFormat: 2-character code (e.g., \"7K\", \"M2\"). Use for alerting/routing, not display." nullable: true readOnly: true errorType: type: string description: "Strictly-typed error type that is explaining the reason of an unsuccessful status of the operation.\r\nAll possible error types are available in the documentation." nullable: true errorData: nullable: true readOnly: true content: allOf: - $ref: '#/components/schemas/NetworkModelResponse' nullable: true additionalProperties: false ApiResultStatus: enum: - ok - serverFailure - permissionDenied - badRequest - notFound - conflict - tooManyRequest - locked - unavailableForLegalReasons type: string NetworkModelResponse: type: object properties: networks: type: array items: $ref: '#/components/schemas/NetworkResponseWithIntegrations' nullable: true additionalProperties: false NetworkResponseWithIntegrations: type: object properties: id: type: string description: >- The Id of the network in Mesh system. Should be used to initiate transfers. format: uuid name: type: string description: The name if the network. nullable: true chainId: type: string description: >- The Inner id of the chain, used for reference. For example, Polygon's (MATIC) chain Id is 137. nullable: true logoUrl: type: string description: Network logo URL. nullable: true supportedTokens: type: array items: type: string description: >- The list of tokens that are currently supported to be transferred using the network. nullable: true nativeSymbol: type: string description: The symbol of the network's native cryptocurrency. nullable: true networkType: enum: - unknown - evm - solana - bitcoin - cardano - tron - avalancheX - tezos - dogecoin - ripple - stellar - litecoin - sui - aptos - tvm - injective allOf: - $ref: '#/components/schemas/NetworkType' description: Network type. tokens: type: array items: $ref: '#/components/schemas/NetworkResponseToken' description: >- The list of tokens that are currently supported to be transferred using the network. nullable: true supportedBrokerTypes: type: array items: $ref: '#/components/schemas/BrokerType' description: >- The list of types of integrations that are currently supported to perform transfers over the network. nullable: true addressPattern: type: string description: >- Optional. The regex pattern for validating addresses on this network. nullable: true additionalProperties: false description: Crypto network. NetworkType: enum: - unknown - evm - solana - bitcoin - cardano - tron - avalancheX - tezos - dogecoin - ripple - stellar - litecoin - sui - aptos - tvm - injective type: string NetworkResponseToken: type: object properties: symbol: type: string description: Token symbol. nullable: true logoUrl: type: string description: Token logo URL. nullable: true contractAddress: type: string description: Optional. The contract address for this token on the network. nullable: true additionalProperties: false description: Token information for a network. BrokerType: enum: - robinhood - eTrade - alpaca - tdAmeritrade - weBull - stash - interactiveBrokers - public - coinbase - kraken - coinbasePro - cryptoCom - openSea - binanceUs - gemini - cryptocurrencyAddress - cryptocurrencyWallet - okCoin - bittrex - kuCoin - etoro - cexIo - binanceInternational - bitstamp - gateIo - acorns - okx - bitFlyer - coinlist - huobi - bitfinex - deFiWallet - krakenDirect - vanguard - binanceInternationalDirect - bitfinexDirect - bybit - paxos - coinbasePrime - btcTurkDirect - kuCoinDirect - okxOAuth - paribuDirect - robinhoodConnect - blockchainCom - bitsoDirect - binanceConnect - binanceOAuth - revolutConnect - binancePay - bybitDirect - paribuOAuth - payPalConnect - binanceTrDirect - coinbaseRamp - bybitDirectMobile - sandbox - cryptoComPay - bybitEuDirect - uphold - binancePayOnchain - sandboxCoinbase - bybitPay - bluvoKrakenOAuth - cashApp type: string securitySchemes: Client-Secret: type: apiKey description: Contact Mesh to get client Secret name: X-Client-Secret in: header Client-Id: type: apiKey description: Contact Mesh to get client Id name: X-Client-Id in: header ````