Skip to main content
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)

{
  "api_key": "sk_live_...",
  "tx_id": "tx_2c4f2b01-5f49-4c66-b379-a9e0c7df8f5e"
}

​
Request (by on-chain hash)

{
  "api_key": "sk_live_...",
  "tx_id": "0x3f9d0b55c8122df4d6d2b41cb6c90a3f7bf8f4f8d4f3c7d1a5b2c3d4e5f6a7b8"
}
FieldTypeRequiredNotes
api_keystring✓Customer API key.
tx_idstring✓Provide either the 1151 transaction ID (tx_<uuid>) or the blockchain transaction hash.
The API automatically detects whether tx_id looks like a UUID-backed identifier or an on-chain hash, so you do not need to set a separate flag.

​
Response

{
  "transaction": {
    "id": "tx_2c4f2b01-5f49-4c66-b379-a9e0c7df8f5e",
    "created_at": 1712609133,
    "associated_wallet": "w_c8b07c7d-9c7d-4a33-9200-0bdfa82dc497",
    "direction": "outbound",
    "amount": "0.05000000",
    "asset": "BTC",
    "destination": "bc1p...",
    "testnet": false,
    "content": "eaw29e...",
    "success": true,
    "metadata": {
      "invoice": "INV-42",
      "customer_id": "cust_123"
    }
  }
}
  • 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

{
  "error": "Transaction not found"
}
Returned with HTTP 404 when neither the ID nor the hash matches a transaction belonging to your account.

​
Errors

StatusPayloadWhen 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.

​
Examples

from py_1151 import Client

client = Client(api_key="sk_live_...")

transaction = client.get_transaction("tx_2c4f2b01-5f49-4c66-b379-a9e0c7df8f5e")

print(transaction.id, transaction.direction, transaction.metadata)
Use whichever identifier you have (1151 ID or on-chain hash); the SDK helpers mirror the REST behaviour and surface the same metadata fields.