---
title: "Paginated journal-line drill-down for a GL account"
method: GET
path: "/companies/{companyId}/reports/general-ledger/{accountId}/entries"
tags: ["Reports"]
---

# Paginated journal-line drill-down for a GL account

`GET /companies/{companyId}/reports/general-ledger/{accountId}/entries`

## Request

- Base URL: `https://api.medianfi.com/api/v1`
- URL: `https://api.medianfi.com/api/v1/companies/{companyId}/reports/general-ledger/{accountId}/entries`
- Auth: HTTP bearer

Returns all journal lines that hit the account, sorted chronologically, with a running balance per the account's normal balance. Supports date-window filtering and cursor pagination.

## Query parameters

- `entityId` string, uuid
- `reportingScopeId` string, uuid
- `scopeAsOf` string, date
- `startDate` string, date
- `endDate` string, date
- `classId` string
- `limit` integer
- `cursor` string

## Response `200`

Paginated drill-down payload

- object
  - `success` boolean
  - `data` object
    - `items` object[]
    - `ledgerRevision` string, nullable: Opaque token of the posted ledger state the report was read under (#1166). It changes whenever any journal entry or line of the company (with `entityId`, of that entity and of entries with no entity) is inserted, updated, voided or deleted, backdated or not. Two reads with equal tokens saw the same ledger. Null when the ledger moved on both attempts of the read, so a client combining pages or statements must treat the result as unproven and retry. Not a credential; not ordered.
  - `meta` object
    - `nextCursor` string, nullable
    - `hasMore` boolean

## Other responses

- `401`: Authentication required
- `422`: Explicit financial scope is required, or the resolved consolidated report is not yet available

---

[API](https://skmtc.dev/medianfi/apis/median-api.md) · [All operations](https://skmtc.dev/medianfi/apis/median-api/llms.txt) · [OpenAPI document](https://skmtc.dev/medianfi/apis/median-api/revisions/20090ea32b0d?raw)