Skip to main content

Ethereum RPC API

Wrap any RPC API call with the ethereum.request() method.

The RPC API builds on top of the API exposed by all Ethereum clients, adding some additional methods.

Ethereum JSON-RPC API Methods

See the full Ethereum JSON-RPC API spec in the Ethereum wiki.

Pay particular attention to these methods:

Additional API Methods



This method is specified by EIP-3085.

Exodus does not yet support adding chains dynamically.

If the chain is already supported by Exodus, the request will succeed.

In any other case, Exodus will reject this request.



This method is specified by EIP-3326.

Switches to the chain with the specified chain ID.

Unlike other wallets like MetaMask, Exodus is stateless. This means that there is no concept of "active chain" at the wallet level. When a web3 site requests switching the chain, the change only affects that site. Switching to a different chain does not prompt the user for confirmation. Instead, the "active chain" (from the web3 site's point of view) is displayed when asking for approval when signing transactions or messages.

Exodus will reject the request under the following circumstances:

  • If the chain ID is malformed.
  • If the chain with the specified chain ID is not supported by Exodus.

See the list of chains supported by Exodus.


  • Array

    1. SwitchEthereumChainParameter - Metadata about the chain that Exodus will switch to.
interface SwitchEthereumChainParameter {
chainId: string // A 0x-prefixed hexadecimal string.


null - The method returns null if the request was successful, and an error otherwise.

If the error code (error.code) is 4902, then the requested chain is not supported by Exodus.


try {
await window.exodus.ethereum.request({
method: 'wallet_switchEthereumChain',
params: [{ chainId: '0x89' }],
} catch (switchError) {
// This error code indicates that the chain is not supported by Exodus.
if (switchError.code === 4902) {
// Handle chain not supported.
// Handle other "switch" errors.