Query Supported Blockchains | On-Chain Data Lookup & Wallet API Integration

·

In the fast-evolving world of Web3, seamless access to blockchain networks is essential for developers building decentralized applications (dApps), digital wallets, or asset management tools. One of the foundational steps in integrating blockchain functionality is understanding which chains are supported by your chosen infrastructure provider. This guide walks you through how to query supported blockchains using a robust Wallet-as-a-Service (WaaS) API, enabling real-time on-chain data lookup and cross-chain interoperability.

Whether you're working with Ethereum, Bitcoin, or emerging Layer 2 networks, knowing the available chains—and their metadata like logo URLs and chain identifiers—is crucial for creating intuitive user experiences in wallet development and asset tracking.

Understanding the Supported Chains Endpoint

The /supported-chains endpoint allows developers to retrieve a comprehensive list of blockchain networks currently supported by the Wallet API. This includes core information such as:

This data can be used to dynamically render network options in your app’s UI, auto-detect compatible wallets, or validate transactions before submission.

👉 Discover how to integrate blockchain support into your app with powerful Web3 tools.

Request Details

No request parameters are required—this is a simple, stateless call that returns the latest list of supported chains.

Response Parameters

Each item in the response includes the following fields:

This structured format ensures easy parsing and integration into frontend components or backend logic.

Example Request

Here's how to make the API call using curl:

curl --location --request GET 'https://web3.okx.com/api/v5/wallet/chain/supported-chains' \
--header 'Content-Type: application/json' \
--header 'OK-ACCESS-PROJECT: 86af********d1bc' \
--header 'OK-ACCESS-KEY: 37c541a1-****-****-****-10fe7a038418' \
--header 'OK-ACCESS-SIGN: leaV********3uw=' \
--header 'OK-ACCESS-PASSPHRASE: 1****6' \
--header 'OK-ACCESS-TIMESTAMP: 2023-10-18T12:21:41.274Z'

Authentication headers are required, including your project ID, API key, signature, passphrase, and timestamp—ensuring secure access to the service.

Example Response

{
  "code": "0",
  "data": [
    {
      "name": "Ethereum",
      "logoUrl": "http://www.eth.org/eth.png",
      "shortName": "ETH",
      "chainIndex": "1"
    }
  ],
  "msg": ""
}

A successful response returns a "code": "0" indicating no errors, with the chain list nested under the data array. You can loop through this array to populate dropdown menus, filter transaction histories, or build dynamic network switchers.

Why Querying Supported Chains Matters

Dynamic chain detection enhances both security and usability. Instead of hardcoding network lists, your application stays up-to-date automatically whenever new blockchains are added. For instance:

Additionally, having standardized identifiers like chainIndex simplifies database modeling and reduces integration complexity when supporting dozens of chains.

👉 Learn how real-time chain data improves wallet functionality and user trust.

Best Practices for Implementation

  1. Cache Responsibly: While the list doesn't change frequently, avoid calling this endpoint on every page load. Cache results for several hours unless immediate freshness is required.
  2. Handle Empty Responses Gracefully: Always check if data is present and non-empty before rendering UI elements.
  3. Use HTTPS for Logo URLs: Ensure any logos fetched from logoUrl are loaded securely to prevent mixed-content warnings.
  4. Monitor for Updates: Subscribe to API changelogs so you're aware when new chains are added or deprecated.

Core Keywords for SEO and Developer Discovery

To ensure this content reaches its intended audience—Web3 developers, product architects, and blockchain engineers—we've naturally integrated the following core keywords:

These terms align with common search queries related to blockchain development tooling and API usage.

Frequently Asked Questions

How often is the list of supported chains updated?

The list is updated regularly as new blockchains are integrated into the platform. There’s no fixed schedule, so it's best to implement periodic checks (e.g., daily or weekly) or rely on cached data with fallback refresh logic.

Can I use the chainIndex for transaction signing?

Yes, the chainIndex is often used to specify the correct network context during transaction signing and broadcasting. Always confirm its role in other API endpoints like /create-transaction or /sign-message.

Is there a limit to how many times I can call this endpoint?

Typically, rate limits apply to all API endpoints. While this specific call is lightweight, excessive polling may trigger throttling. Refer to the official documentation for exact limits per minute or hour.

Does the response include testnet networks?

Currently, only mainnet chains are included in the /supported-chains response. Testnet support must be verified separately via developer documentation or sandbox environments.

Can I request additional metadata like RPC endpoints or block explorers?

Not through this endpoint. However, extended chain details such as RPC URLs, consensus type, or explorer links may be available in other parts of the Web3 API suite. Explore related endpoints for full ecosystem data.

What should I do if a chain I need isn't listed?

If a major blockchain is missing, consider reaching out through official developer channels or checking for upcoming roadmap announcements. Community feedback often influences future integrations.

👉 Access comprehensive Web3 APIs with full blockchain support and documentation.