# Ledger by Novadyne – Get Transaction by ID

> Ledger by Novadyne – Get Transaction by ID is a paid API for AI agents from ledger-api.novadyne.ai, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-12).

Retrieves a specific double-entry ledger transaction by its numeric ID, returning the transaction date and its journal entries.

## Facts

- Endpoint: GET https://ledger-api.novadyne.ai/ledger/transactions/%7Btx_id%7D
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ledger-by-novadyne-get-transaction-by-id-a72731b3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NMcaw366GYIStutcVQMFC

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability ledger-by-novadyne-get-transaction-by-id-a72731b3
```

Example prompt: Pull up transaction 1042 from the Novadyne double-entry ledger and show me its date and all the journal entries.

## When to prefer this

Use this endpoint when you need to retrieve the full details of a single, known double-entry ledger transaction by its numeric ID from the Novadyne ledger system, especially in contexts where x402 micropayments and Ed25519 capability tokens are already supported in your agent stack.

## Known failure modes

- Transaction ID not found — 404 or empty response if the tx_id does not exist in the ledger
- Invalid tx_id type — error if a non-integer is provided as the transaction ID
- Payment failure — x402 payment of $0.002 USDC not processed, request rejected
- Unauthorized — Ed25519 capability token missing, invalid, or expired
- Server error — 5xx if the ledger service is temporarily unavailable

## How this service works

Double-entry ledger API with x402 micropayments and Ed25519 capability tokens.

## Output

Returns a JSON object containing the transaction's numeric ID, its date string, and an array of double-entry journal entries (debits and credits) associated with that transaction.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "tx_id"
 ],
 "properties": {
  "tx_id": {
   "type": "integer",
   "description": "Transaction ID (path parameter)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "id": {
   "type": "integer"
  },
  "date": {
   "type": "string"
  },
  "entries": {
   "type": "array"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ledger-by-novadyne-get-transaction-by-id-a72731b3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from ledger-api.novadyne.ai](https://www.zero.xyz/host/ledger-api.novadyne.ai/llms.txt)