Skip to main content
Socket enables bridging, where an asset on one chain is transferred or converted into an asset on another chain in one seamless step. Users sign on the source chain; Socket handles route discovery, bridge execution, and delivery.

​
Bridge with Socket

Socket is built for apps that need cross-chain transfers without sending users away to compare bridge routes manually:
  • Best route selection: Compare bridge and swap paths by output, speed, and reliability.
  • Any-chain delivery: Move assets across supported EVM and non-EVM networks from one integration.
  • Flexible route control: Use routeTags like SUGGESTED, FASTEST, and MAX_OUTPUT to match user preferences.
  • Large or small transfers: Route user deposits, wallet transfers, treasury movement, and settlement flows through the same API.

​
Who this is for

Use bridging when users need funds on another network, when an app wants to fund its destination chain without breaking the flow, or when teams need programmatic cross-chain transfers for operations and settlement.

​
How it works

  1. The user requests a quote specifying originChainId and destinationChainId (different values).
  2. Socket routes through a marketplace of off-chain agents — fillers, solvers, and provers — competing to execute the best route.
  3. The winning agent bridges the asset and delivers the output token to receiverAddress on the destination chain.

​
Supported bridge providers

Provider IDDisplay name
staked-relayRelay
staked-acrossAcross
staked-gnosis-nativeGnosis Native
staked-polygon-nativePolygon Native
staked-native-op-stackOP Stack Native
cctp-v2Circle CCTP V2
staked-celerCeler
cctp-v2-slowCircle CCTP V2 Slow
staked-arbitrum-nativeArbitrum Native Bridge
staked-oftOFT
staked-mayanMayan
staked-scroll-nativeScroll Native

​
Example

curl -sS -G "https://dedicated-backend.socket.tech/v3/swap/quote" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "affiliate: YOUR_AFFILIATE_ID" \
  --data-urlencode "userOps=tx" \
  --data-urlencode "originChainId=8453" \
  --data-urlencode "destinationChainId=42161" \
  --data-urlencode "inputToken=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913" \
  --data-urlencode "outputToken=0xaf88d065e77c8cC2239327C5EDb3A432268e5831" \
  --data-urlencode "inputAmount=1000000" \
  --data-urlencode "userAddress=0x1111111111111111111111111111111111111111" \
  --data-urlencode "receiverAddress=0x1111111111111111111111111111111111111111" \
  --data-urlencode "slippage=1"

​
Supported chains

Check the Chain Support page for the full list of supported networks.

​
Key rules

  • receiverAddress must be a valid address on the destination chain.
  • If approval is present in the response, approve the spender before submitting txData.
  • Use routeTags (SUGGESTED, FASTEST, MAX_OUTPUT) to help users pick the best route.
  • Check expiresAt before submitting — do not send expired quotes.

API Integration Guide

Full guide to integrating the Socket Swap V3 API

Chain Support

See which chains are supported