Skip to main content

Get Bridge Tunnel List

GET 

/2.0/bridge-tunnels

Retrieves the list of available bridge tunnels.

What is a bridge tunnel?​

A bridge tunnel is a pre-registered route that defines which coin can be sent from which platform to which platform. Only routes that Octet has verified and approved in advance are listed, and each tunnel combines the following information.

1) Routing​

FieldMeaning
sourcePlatform / destinationPlatformSource/destination chains (e.g., Ethereum, Arbitrum)
sourceCoin / destinationCoinSource/destination coins (e.g., USDC)

2) Bridge protocol​

The bridgeProtocol field: the bridge service used to move the asset. Examples: CCTP (Circle, USDC only), Stargate (LayerZero-based), Wormhole, etc. Each protocol works differently and has its own fee structure (CCTP: burn → attestation → mint / Stargate: LP pools / Wormhole: guardian signatures, etc.).

3) Required transaction steps (need* flags)​

Each need* flag indicates whether a step must run for a bridge to complete. The Octet scheduler runs these steps automatically, but input and balance validation and the destination address policy depend on these flags.

FlagChainMeaning
needApproveErc20SourcesourceWhether an ERC20 approve transaction is needed so the bridge contract can pull the token
needBridgeSourcesourceWhether a transaction that executes the bridge on the source chain is needed (e.g., CCTP depositForBurn, Stargate send)
needActivateAddressDestinationdestinationWhether a transaction that activates or registers the receiving address on the destination chain is needed (some chains require a new address to be activated before its first use)
needBridgeDestinationdestinationWhether a finalizing transaction is needed on the destination chain to receive the asset (e.g., minting with CCTP receiveMessage)

The destination address of a bridge must always be a main address in the same account. If either needActivateAddressDestination or needBridgeDestination is true, Octet must send transactions on the destination chain, so the destination balance is validated; if the destination wallet's key management type is multisig (co-managed), encryptedDestinationUserKey must also be submitted.

Use in bridge requests​

The Request Bridge API requires bridgeTunnelIdx. Find the route you want in this API's response and pass its idx.

Optional filters​

  • sourcePlatformIdx : filter by source platform (e.g., Ethereum)
  • destinationPlatformIdx : filter by destination platform (e.g., Arbitrum)

Request​

Responses​

Success