Comment on page

Chains

Returns list of chains supported by Socket APIs

/v2/supported/chains
How this endpoint is to be used :
List of sending chain options and destination chain options is to be populated using this endpoint. For reference, check out the Bungee App​
API-KEY needs to be passed in the headers while making the GET request
get
https://api.socket.tech/v2
/supported/chains
Returns list of chains supported
Note : If sendingEnabled parameter is false,the chain isn't supported on the sending side. Hence, it needs to be excluded as an option on the Sending Chain selection list.
Note : If receivingEnabled parameter is false,the chain isn't supported on the receiving side. Hence, it needs to be excluded as an option on the Receiving/Destination Chain selection list.
Description of response parameters
Parameter
Description
success
Indicates successful response from endpoint, as intended.
chainId
ID of chain, for example Optimism = 10
name
Name of chain
isL1
Identifies if chain is a layer 1 chain.  false for layer 2 chains (Optimism, BSC, xDAI, Polygon, Fantom, Arbitrum) and true for base layer (Ethereum)
sendingEnabled
Determines if this chain is supported on the sending side. If true it can be shown as an option on sending chain selection list.
icon
URL to icon/logo of chain
receivingEnabled
Determines if this chain is supported on the receiving end. If true it can be shown as an option on receiving/destination chain selection list.
refuel.sendingEnabled
Determines if Refuel feature is supported with given chain on source side
refuel.receivingEnabled
Determines if Refuel feature is supported with given chain on destination side
currency
Object with metadata of native token of chain
currency.address
Address of native token OR gasPayingAsset, which default is 0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
currency.icon
URL of native token icon
currency.name
Name of native token
currency.symbol
Symbol of native token
currency.decimals
Decimal places for amount supported by token
currency.minNativeCurrencyForGas
Minimum amount of native token needed on the chain to execute a Socket transaction
rpcs
Array of RPC endpoints to connect with
explorers
Array of block explorers URLs supporting a given chain
​
Test your query on the Socket Swagger interface : https://api.socket.tech/v2/swagger/#/Supported/SupportedController_getAllSupportedRoutes​

Parameter	Description
`success`	Indicates successful response from endpoint, as intended.
`chainId`	ID of chain, for example Optimism = 10
`name`	Name of chain
`isL1`	Identifies if chain is a layer 1 chain. `false` for layer 2 chains (Optimism, BSC, xDAI, Polygon, Fantom, Arbitrum) and `true` for base layer (Ethereum)
`sendingEnabled`	Determines if this chain is supported on the sending side. If `true` it can be shown as an option on sending chain selection list.
`icon`	URL to icon/logo of chain
`receivingEnabled`	Determines if this chain is supported on the receiving end. If `true` it can be shown as an option on receiving/destination chain selection list.
`refuel.sendingEnabled`	Determines if Refuel feature is supported with given chain on source side
`refuel.receivingEnabled`	Determines if Refuel feature is supported with given chain on destination side
`currency`	Object with metadata of native token of chain
`currency.address`	Address of native token OR gasPayingAsset, which default is `0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee`
`currency.icon`	URL of native token icon
`currency.name`	Name of native token
`currency.symbol`	Symbol of native token
`currency.decimals`	Decimal places for amount supported by token
`currency.minNativeCurrencyForGas`	Minimum amount of native token needed on the chain to execute a Socket transaction
`rpcs`	Array of RPC endpoints to connect with
`explorers`	Array of block explorers URLs supporting a given chain

Bridges

Token Support

Last modified 1yr ago