Skip to main content
POST
Build CCIP token bridge instructions

Authorizations

X-API-Key
string
header
required

API Key required to access Supertransaction API. Example: mee_2w3mXCuyt4xVXDRCZ5k5Lhgs

Body

application/json

Body

Object containing the CCIP token bridging field, including source/destination tokens and chains, user address, amount, execution mode, and slippage tolerance.

srcToken
string
required

Source token EVM address. Must be a valid checksummed Ethereum address.

Example:

"0x833589fcd6edb6e08f4c7c32d4f71b54bda02913"

dstToken
string
required

Destination token EVM address. Must be a valid checksummed Ethereum address.

Example:

"0x94b008aa00579c1307b0ef2c499ad98a8ce58e58"

srcChainId
number
required

The source chain ID for the swap or token bridging. Use a supported chain ID number.

Example:

8453

dstChainId
number
required

The destination chain ID for the swap or token bridging. Use a supported chain ID number.

Example:

10

ownerAddress
string
required

EOA wallet address which is going to be used as a owner of orchestrator account

Example:

"0x742d35cc6639cb8d4b5d1c5d7b8b5e2e7c0c7a8a"

amount
object
required

Schema for specifying a runtime ERC20 balance check, including the target address, token address, and optional constraints.

mode
enum<string>
required
Available options:
smart-account,
eoa,
eoa-7702
gasLimit
string

Gas limit for the CCIP token bridging

Example:

"50000"

Response

200

instructions
object[]
required

Array of MEE instructions ready for execution

simulationTokenOverrides
object[]