Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Track a Message

Use this API to check source and destination status for a cross-chain message.

Endpoint

  • Method: GET
  • URL: https://api.v2.concero.io/api/v1/scan/tx

Required query strategy

Provide at least one primary filter:

  • messageId
  • srcHash
  • dstHash
  • sender
  • receiver

Optional pagination:

  • take
  • skip

Quick examples

Query by messageId

curl -X GET \
  'https://api.v2.concero.io/api/v1/scan/tx?messageId=0xYOUR_MESSAGE_ID&take=1&skip=0' \
  -H 'accept: application/json'

Query by source tx hash

curl -X GET \
  'https://api.v2.concero.io/api/v1/scan/tx?srcHash=0xYOUR_SOURCE_TX_HASH&take=10&skip=0' \
  -H 'accept: application/json'

Expected Response

{
  "code": "ok",
  "payload": {
    "transactions": [
      {
        "id": "0x...",
        "status": "success",
        "from": {
          "chain": { "id": 421614, "name": "Arbitrum Sepolia" },
          "hash": "0x...",
          "timestamp": 1758708525
        },
        "to": {
          "chain": { "id": 43113, "name": "Avalanche Fuji" },
          "hash": "0x...",
          "timestamp": 1758708536
        }
      }
    ],
    "pagination": { "skip": 0, "take": 1 }
  }
}

Interpretation:

  • id: message ID.
  • status: current high-level state.
  • from.hash: source-chain transaction hash.
  • to.hash: destination-chain transaction hash (when delivered).

Suggested workflow

  1. Save messageId returned by conceroSend.
  2. Poll by messageId until status is terminal.

If status stalls or fails, check Troubleshooting.