---
title: "Get transaction from a ledger by its ID"
method: GET
path: "/v2/{ledger}/transactions/{id}"
tags: ["ledger.v2"]
---

# Get transaction from a ledger by its ID

`GET /v2/{ledger}/transactions/{id}`

## Path parameters

- `ledger` string, required
- `id` integer, required

## Query parameters

- `expand` string
- `pit` string, date-time

## Response `200`

OK

- V2GetTransactionResponse
  - `data` V2Transaction, required — A transaction recorded in the ledger, carrying its postings, metadata and both bi-temporal timestamps
    - `insertedAt` string, date-time — The request time: when the transaction was actually written to the ledger. Set by the ledger, not the caller. See [bi-temporality](https://docs.formance.com/modules/ledger/working-with/bi-temporality)
    - `updatedAt` string, date-time — When the transaction row was last modified, for example by a metadata change or a revert
    - `timestamp` string, date-time, required — The transaction time: when the transaction is considered to have occurred, also called the effective or booking date. This is the axis the ledger uses to compute balances and resolve point-in-time queries. Settable at creation, defaulting to current machine time if omitted, and immutable once written. See [bi-temporality](https://docs.formance.com/modules/ledger/working-with/bi-temporality)
    - `postings` V2Posting[], required — The fund movements making up the transaction
      - `amount` integer, required — Amount to move, as an arbitrary-precision integer expressed in the asset's smallest unit
      - `asset` string, required — The asset being moved, optionally carrying a scale suffix such as USD/2
      - `destination` string, required — Address of the account credited by this posting
      - `source` string, required — Address of the account debited by this posting
    - `reference` string — Optional caller-supplied identifier, unique within the ledger, used to deduplicate transactions
    - `metadata` V2Metadata, required — Arbitrary key/value pairs attached to the resource. Metadata is bi-temporal, so a point-in-time query returns the metadata as it stood at that time
    - `id` integer, required — Unique sequential identifier for this transaction within the ledger
    - `reverted` boolean, required — Indicates if the transaction has been reverted
    - `revertedAt` string, date-time — When the transaction was reverted, on the request-time axis. Absent if the transaction has not been reverted
    - `preCommitVolumes` V2AggregatedVolumes — Volumes aggregated per account and per asset
    - `postCommitVolumes` V2AggregatedVolumes — Volumes aggregated per account and per asset
    - `preCommitEffectiveVolumes` V2AggregatedVolumes — Volumes aggregated per account and per asset
    - `postCommitEffectiveVolumes` V2AggregatedVolumes — Volumes aggregated per account and per asset
    - `template` string — Name of the transaction template this transaction was created from, if any

## Other responses

- `default` — Error

---

[API](https://skmtc.dev/formancehq/apis/ledger-api.md) · [All operations](https://skmtc.dev/formancehq/apis/ledger-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/formancehq/ledger-api/revisions/fe945da1b75d/schema)