Skip to main content
GET

Overview

This endpoint retrieves blockchain network configuration required to implement wallet delegation in your frontend application. Use this data before initiating the delegation flow to get the correct contract addresses and chain IDs for the user’s selected network.
When to Use: Call this endpoint before Step 2 of the delegation workflow to get the correct contract addresses, chain IDs, and spender addresses for building approval transactions in the user’s wallet provider.

What You’ll Get

  • Chain IDs for each supported network (Linea, Ethereum)
  • Token contract addresses (USDC, USDT) for each network
  • Platform spender addresses that users will approve for token spending
  • Network-specific configuration for building approval transactions
  • Solana token mint addresses and delegate address

Use Case

Use this configuration data in your frontend (Step 2 of delegation) to construct the correct approval transaction with the right contract addresses and chain ID for the user’s wallet provider.

Authentication

string
required
Your public client key for API authentication
string
required
Bearer token format: Bearer {access_token}

Query Parameters

string
Filter by network name to get configuration for a specific blockchain network.Supported values: ethereum, linea, solana, etherlinkExample: ?network=ethereumNote: If not specified, returns configuration for all supported networks.
string
Region identifier for environment routing. Use us for US-specific Linea routing.Example: ?region=us
Alternatively, you can use the x-us-env: true header instead of the region query parameter.

Response

array
required
Array of network configurations matching the query filters
integer
required
Number of networks returned in the responseExample: 1 (when filtering by network), 3 (when getting all networks)
HATEOAS links for API navigation

Response Codes

Implementation Example

Here’s how to use this endpoint in a complete delegation workflow:
TypeScript Implementation

Security Best Practices

  • Always verify contract addresses - Compare received addresses against known good addresses
  • Validate address format - Ensure EVM addresses start with 0x and are 42 characters long
  • Check network compatibility - Verify addresses match the intended blockchain network
  • Use checksummed addresses - Apply EIP-55 checksum validation for Ethereum addresses
  • Cache configuration temporarily - Avoid repeated API calls during user session
  • Implement cache invalidation - Refresh configuration periodically or when errors occur
  • Handle network-specific configs - Store separate configurations for different networks
  • Validate before use - Always verify cached configuration is still valid
  • Handle network failures gracefully - Implement retry logic with exponential backoff
  • Provide fallback mechanisms - Have backup methods if configuration loading fails
  • Log configuration issues - Track when configuration retrieval fails for debugging
  • User-friendly error messages - Explain clearly when configuration cannot be loaded

Common Use Cases

Multi-Network Support

Configure your application to support multiple blockchain networks:
TypeScript Multi-Network

Configuration Validation

Validate configuration data before using in transactions:
JavaScript Validation

Further Reading