Honeycluster Docs – Look up a transaction by hash

network

Look up a transaction by hash

get

/ledger/tx/{hash}

operationId: network-ledgerTx

Live transaction lookup by hash. Given a 64-char hex hash, returns the raw transaction body plus metadata as reported by the ledger. No database lookup or enrichment — consumers needing indexed views should use the trade/NFT/account endpoints instead.

Authorizations

Name	Location	Details
`BearerAuth`	Authorization header · bearer	JWT issued by the Honeycluster auth service for the `indexer` audience. Present as `Authorization: Bearer <token>`.

Path Parameters

Name	Type	Default	Description
`hash` required	string		64-character hex transaction hash to look up on the ledger.

Responses

200

application/json

Successful response

Field	Type	Description
`hash`	string	Transaction hash echoed back.
`ledgerIndex`	integer	Ledger index the transaction was included in (omitted for pending lookups).
`closeTimeIso`	string	Close-time of the including ledger as an ISO 8601 timestamp.
`date`	integer	Ripple-epoch close time of the including ledger (seconds since 2000-01-01).
`validated`	boolean	True when the transaction is in a validated ledger.
`ctid`	string	Concise transaction identifier when available.
`tx`	object	Raw `tx_json` (or legacy top-level transaction fields) as returned by the ledger.
`meta`	object	Raw transaction metadata as returned by the ledger (omitted when unavailable).

Example

Json

{
  "hash": "E94F30E2D44807C006B7F7C06A4E6CAE4B63BD89BB1B7C90CCFB85B6D82735CF",
  "ledgerIndex": 103801288,
  "closeTimeIso": "2026-04-25T13:11:07Z",
  "date": 830956267,
  "validated": true,
  "ctid": "C062F4480000537A",
  "tx": {
    "TransactionType": "Payment",
    "Account": "rExampleSender123",
    "Destination": "rExampleReceiver456",
    "Amount": "1000000",
    "Fee": "12",
    "Sequence": 4501
  },
  "meta": {
    "TransactionResult": "tesSUCCESS",
    "delivered_amount": "1000000"
  }
}

400

application/json

Invalid input data

Field	Type	Description
`message`	string	The error message
`code`	string	The error code
`issues`	object[]	An array of issues that were responsible for the error
`issues[].message`	string

Example

Json

{
  "code": "BAD_REQUEST",
  "message": "Invalid input data",
  "issues": []
}

401

application/json

Authorization not provided

Field	Type	Description
`message`	string	The error message
`code`	string	The error code
`issues`	object[]	An array of issues that were responsible for the error
`issues[].message`	string

Example

Json

{
  "code": "UNAUTHORIZED",
  "message": "Authorization not provided",
  "issues": []
}

403

application/json

Insufficient access

Field	Type	Description
`message`	string	The error message
`code`	string	The error code
`issues`	object[]	An array of issues that were responsible for the error
`issues[].message`	string

Example

Json

{
  "code": "FORBIDDEN",
  "message": "Insufficient access",
  "issues": []
}

404

application/json

Not found

Field	Type	Description
`message`	string	The error message
`code`	string	The error code
`issues`	object[]	An array of issues that were responsible for the error
`issues[].message`	string

Example

Json

{
  "code": "NOT_FOUND",
  "message": "Not found",
  "issues": []
}

500

application/json

Internal server error

Field	Type	Description
`message`	string	The error message
`code`	string	The error code
`issues`	object[]	An array of issues that were responsible for the error
`issues[].message`	string

Example

Json

{
  "code": "INTERNAL_SERVER_ERROR",
  "message": "Internal server error",
  "issues": []
}