POST /transaction/get
Returns an individual transaction recorded by 1151.
Provide whichever identifier you have—either the 1151 transaction ID or the on-chain hash—in the single tx_id
field.
Request (by transaction ID)
Request (by on-chain hash)
Field | Type | Required | Notes |
---|---|---|---|
api_key | string | ✓ | Customer API key. |
tx_id | string | ✓ | Provide either the 1151 transaction ID (tx_<uuid> ) or the blockchain transaction hash. |
tx_id
looks like a UUID-backed identifier or an on-chain hash, so you do not need to set a separate flag.
Response
- When a record is found the payload includes the transaction metadata exactly as stored by the platform (
null
when omitted). associated_wallet
links back to the wallet resource so you can join transactions to balances.- Transactions associated with test wallets return
"testnet": true
.
Not found response
Errors
Status | Payload | When it happens |
---|---|---|
400 | { "error": "Missing required fields" } | tx_id omitted or blank. |
403 | { "error": "API key is not valid" } | API key fails validation. |
404 | { "error": "Transaction not found" } | No transaction matched the parameters for your account. |
500 | { "error": "<message>" } | Unexpected service error. |
SDK equivalents
- JavaScript:
client.getTransaction({ txId })
- Python:
client.get_transaction(identifier)