Get OP hook

Generates OP hook data required for certain cross-chain routes that involve Optimistic bridge withdrawals with ERC-20 token conversion. When the Compute Route response includes required_op_hook: true, you must call this endpoint to obtain the hook payload before generating transaction messages.

Pass the returned hook data to the Generate Transaction endpoint (POST /v2/fungible/msgs) in the signed_op_hook field after signing it.

POST /op-hook

Get OP hook

cURL

curl --request POST \
  --url https://router-api.initia.xyz/op-hook \
  --header 'Content-Type: application/json' \
  --data '
{
  "source_address": "init1abc...",
  "source_asset_chain_id": "echelon-1",
  "source_asset_denom": "uinit",
  "dest_address": "0xdef...",
  "dest_asset_chain_id": "8453",
  "dest_asset_denom": "0x..."
}
'

200

{
  "chain_id": "8453",
  "hook": []
}

Body

application/json

source_address · string · required

Sender address on the source chain.

source_asset_chain_id · string · required

Source chain ID.

source_asset_denom · string · required

Source asset denomination.

dest_address · string · required

Recipient address on the destination chain.

dest_asset_chain_id · string · required

Destination chain ID.

dest_asset_denom · string · required

Destination asset denomination.

Response

200

application/json

Successful response

chain_id · string

Chain ID where the hook messages should be executed.

hook · object[]

Array of EVM messages that form the OP hook payload.