---
title: "List the ledger lines posted against an order"
method: GET
path: "/shop/orders/{orderId}/ledger-lines"
tags: ["Orders"]
---

# List the ledger lines posted against an order

`GET /shop/orders/{orderId}/ledger-lines`

List every ledger line posted against an order, sorted by
`ledger_date` ascending. Ledger lines are Trybe's financial
record of an order — one entry per revenue posting, per payment,
per refund and per redemption — and form the audit trail used by
the reporting suite to compute revenue, payment and tax totals.

Each line carries a `revenue_centre` code (and a human-friendly
`revenue_centre_name`), an amount split into `gross_amount` and
`net_amount` in the order's currency, plus references to the
`payable` (the thing being charged — usually an order or a
payment) and the `causer` (the user or system process that
triggered the posting).

The response is not paginated; orders typically have tens of
ledger lines and rarely hundreds.

## Response `200`

The ledger lines for the order.

- object
  - `data` OrderLedgerLine[], required
    - `id` string, object-id, required — The ID of the ledger line.
    - `type` string, required — The kind of posting — for example `revenue`, `payment`, `refund`, `redemption`. Drives how the line is rolled up in reports.
    - `status` string, required — The lifecycle status of the line. `final` is the only value callers should treat as authoritative; non-final lines are provisional and may change before close-of-day.
    - `description` string, nullable, required — Human-readable description of what the line represents — for example the offering name for revenue postings, or the payment processor for payment postings.
    - `gross_amount` integer, required — The gross amount of the line in the lowest denomination of the order's currency (e.g. pennies for `GBP`).
    - `net_amount` integer, required — The net amount of the line — `gross_amount` minus tax — in the lowest denomination of the order's currency.
    - `revenue_centre` string, nullable, required — The revenue centre this line is attributed to. May be a Trybe system code (e.g. `treatments`, `retail`, `service_charge`) or a site-specific code.
    - `revenue_centre_name` string, nullable, required — Human-friendly label for the revenue centre. For Trybe system codes this is a localised name; for site-specific codes it falls back to the code itself.
    - `payment_processor` string, nullable, required — For payment-related lines, the processor used (e.g. `stripe`, `adyen`, `manual`, `pms_folio`).
    - `payment_processor_friendly` string, nullable, required — Human-friendly version of `payment_processor`.
    - `mapped_value` string, nullable — When a PMS or accounting integration maps the revenue centre to its own code, the mapped value is surfaced here. Omitted when no mapping applies.
    - `ledger_date` string, date-time, required — The date the posting was recorded against the ledger. Used for reporting in operational time.
    - `revenue_date` string, date-time, required — The business date the revenue should be recognised against. May differ from `ledger_date` for postings made after revenue recognition cut-off.
    - `currency` string, required — The ISO-4217 currency code.
    - `payable` object, nullable, required — Summary of the entity being charged — typically the order itself for revenue/redemption lines, or a `Payment` for payment/refund lines.
    - `causer` object, nullable, required — Summary of the user or system process that triggered the posting. `null` for postings made by automated background jobs that aren't attributable to a single actor.
    - `created_at` string, date-time, required — When then resource was created.

## Other responses

- `401` — The user is unauthenticated
- `403` — The authenticated user does not have permission.
- `404` — The resource couldn't be found

---

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