Status

Get Transaction Status

post

Shares the node's knowledge of any payloads associated with the given intent hash. Generally there will be a single payload for a given intent, but it's theoretically possible there may be multiple. This knowledge is summarised into a status for the intent. This summarised status in the response is likely sufficient for most clients.

Body

networkstringRequired

The logical name of the network

Example: {{network}}

intent_hashstringRequired

The transaction intent hash for a user transaction, also known as the transaction id. This hash identifies the core "intent" of the transaction. Each transaction intent can only be committed once. This hash gets signed by any signatories on the transaction, to create the signed intent. Either hex or Bech32m-encoded strings are supported.

Responses

200

Transaction status response

application/json

400

Client error

application/json

500

Server error

application/json

post

HTTPcURLJavaScriptPython

POST /lts/transaction/status HTTP/1.1
Host: xrd.nownodes.io
Content-Type: application/json
Accept: */*
Content-Length: 46

{
  "network": "{{network}}",
  "intent_hash": "text"
}

{
  "intent_status": "CommittedSuccess",
  "status_description": "text",
  "committed_state_version": 1,
  "invalid_from_epoch": 1,
  "known_payloads": [
    {
      "payload_hash": "text",
      "payload_hash_bech32m": "text",
      "state_version": 1,
      "status": "CommittedSuccess",
      "error_message": "text"
    }
  ]
}