> ## Documentation Index > Fetch the complete documentation index at: https://docs.onebalance.io/llms.txt > Use this file to discover all available pages before exploring further. # List supported chains > Retrieves a list of all blockchain networks currently integrated with and supported by the OneBalance platform. ## OpenAPI ````yaml get /chains/supported-list openapi: 3.1.0 info: version: 1.6.2 title: OneBalance API description: > # OneBalance API The OneBalance API provides a programmatic interface for managing OneBalance resources using standard HTTP requests. The API documentation includes a design and technology overview, followed by detailed endpoint information. ## Features OneBalance API provides a complete chain abstraction toolkit: - Smart Account Management: Predict addresses and deploy accounts - Cross-Chain Balances: View aggregated balances across multiple chains - Multichain Transactions: Execute transfers and swaps using aggregated balances - Transaction Status: Track multichain transaction history and status - Token Aggregation: Access unified token lists and pricing information Enterprise API Access: Need higher rate limits, dedicated infrastructure, or custom SLAs? [Contact our sales](mailto:sales@onebalance.io) team for enterprise API solutions. ## Base URL OneBalance API is built on REST principles and is served over HTTPS. To ensure data privacy, unencrypted HTTP is not supported. The Base URL for all API endpoints is: ```bash https://be.onebalance.io/api ``` ## Quickstart Try our reference application at [app.onebalance.io](https://app.onebalance.io) to see the API in action or jump straight into our [API Reference](https://docs.onebalance.io/api-reference/account/predict-address) to start building. ## Authentication The OneBalance API uses API keys to authenticate requests. All API requests require authentication using an API key passed in the `x-api-key` header: ```bash curl -X 'GET' \ 'https://be.onebalance.io/api/path-to/endpoint' \ -H 'x-api-key: 42bb629272001ee1163ca0dbbbc07bcbb0ef57a57baf16c4b1d4672db4562c11' ``` A public API key is available for testing purposes with limited usage: **42bb629272001ee1163ca0dbbbc07bcbb0ef57a57baf16c4b1d4672db4562c11** All API requests must be made over [HTTPS](https://en.wikipedia.org/wiki/HTTPS). Calls made over plain HTTP will fail. API requests without authentication will also fail. license: name: Apache 2.0 url: https://www.apache.org/licenses/LICENSE-2.0.html contact: name: OneBalance Support email: support@onebalance.io termsOfService: https://onebalance.io/terms-of-service servers: - url: https://be.onebalance.io/api description: Production environment security: - ApiKeyAuth: [] tags: - name: Account x-displayName: Smart Accounts description: >- Manage and predict addresses for OneBalance smart accounts. These accounts enable features like resource locks and streamlined cross-chain interactions. - name: Assets x-displayName: Aggregated Assets description: >- Retrieve details about supported aggregated assets. Aggregated assets represent a unified view of a token across multiple chains, simplifying cross-chain operations. - name: Balances x-displayName: Aggregated Balances description: >- Access and track aggregated asset balances for user accounts. These balances reflect a user's total holdings of an asset across all supported chains, usable for multichain transactions. - name: Chains x-displayName: Supported Chains description: >- List and get details about the blockchain networks currently integrated with and supported by the OneBalance platform. - name: Status x-displayName: Transaction Status & History description: >- Track the real-time status of quote executions and retrieve complete transaction histories for user accounts, offering visibility into multichain operations. - name: Quotes x-displayName: Quotes & Execution description: >- Request, prepare, and execute quotes for various cross-chain operations including asset transfers, swaps, and arbitrary contract interactions. These endpoints facilitate the core transaction lifecycle on OneBalance. paths: /chains/supported-list: get: tags: - Chains summary: List supported chains description: >- Retrieves a list of all blockchain networks currently integrated with and supported by the OneBalance platform. operationId: supportedChains parameters: [] responses: '200': description: The list of supported chains content: application/json: schema: type: array items: $ref: '#/components/schemas/chain' example: - chain: chain: eip155:42161 namespace: eip155 reference: '42161' isTestnet: false - chain: chain: eip155:8453 namespace: eip155 reference: '8453' isTestnet: false - chain: chain: eip155:10 namespace: eip155 reference: '10' isTestnet: false - chain: chain: eip155:137 namespace: eip155 reference: '137' isTestnet: false - chain: chain: eip155:59144 namespace: eip155 reference: '59144' isTestnet: false - chain: chain: eip155:43114 namespace: eip155 reference: '43114' isTestnet: false - chain: chain: eip155:1 namespace: eip155 reference: '1' isTestnet: false '401': $ref: '#/components/responses/unauthorized' '422': description: Unable to get supported chains content: application/json: schema: $ref: '#/components/schemas/http-exception' example: error: Unprocessable Entity message: Unable to get supported chains statusCode: 422 components: schemas: chain: type: object properties: chain: description: The chain entity representing the blockchain network allOf: - $ref: '#/components/schemas/chain-entity' example: chain: eip155:42161 namespace: eip155 reference: '42161' isTestnet: type: boolean description: Indicates whether the chain is a testnet example: false required: - chain - isTestnet http-exception: type: object properties: error: type: string description: Error name example: Validation failed message: type: string description: Error message example: >- Validation error: Must be a valid hex string starting with 0x at "address" statusCode: type: number description: Error status code example: 400 required: - error - message - statusCode chain-entity: type: object properties: chain: type: string description: >- The full CAIP-2 chain identifier (e.g., `eip155:1` for Ethereum Mainnet). example: eip155:1 namespace: type: string description: The CAIP-2 chain namespace (e.g., `eip155`). example: eip155 reference: type: string description: >- The CAIP-2 chain reference (chain ID) within the namespace (e.g., `1` for Ethereum Mainnet). example: '42161' required: - chain - namespace - reference HttpUnauthorizedException: type: object properties: error: type: string description: Error name example: UnauthorizedException message: type: string description: Error message example: Invalid or missing API key statusCode: type: number description: Error status code example: 401 timestamp: type: string description: Error timestamp example: '2024-12-18T14:38:24.793Z' path: type: string description: Error path example: /api/account/predict-address required: - error - message - statusCode - timestamp - path responses: unauthorized: description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/HttpUnauthorizedException' example: error: UnauthorizedException message: Invalid or missing API key statusCode: 401 timestamp: '2024-12-18T14:38:24.793Z' path: /api/xxx/xxx securitySchemes: ApiKeyAuth: type: apiKey name: x-api-key in: header description: >- The OneBalance API uses API keys to authenticate requests. All API requests require authentication using an API key passed in the `x-api-key` header: ```bash curl -X 'GET' \ 'https://be.onebalance.io/api/path-to/endpoint' \ -H 'x-api-key: ${ONEBALANCE_API_KEY}' \ ... ``` A public API key is available for testing purposes with limited usage: `42bb629272001ee1163ca0dbbbc07bcbb0ef57a57baf16c4b1d4672db4562c11`. All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail. Learn how to generate API access tokens at [OneBalance Docs](https://docs.onebalance.io). ````