---
title: "List statements"
method: GET
path: "/statements-v2/v3/accounts/{accountId}/statements"
tags: ["Statement"]
---

# List statements

`GET /statements-v2/v3/accounts/{accountId}/statements`

## Request

- Base URL: `https://sandbox.pismolabs.io`
- URL: `https://sandbox.pismolabs.io/statements-v2/v3/accounts/{accountId}/statements`
- Auth: HTTP bearer

List account statements. For more information about statements, refer to [Understanding statements](doc:understanding-statements).

The filter parameters have the following order of precedence:
1. `startFromCurrentCycle`
2. `presentToFront`
3. `presentToPast`

That is, if `startFromCurrentCycle` is `true`, then `presentToFront` and `presentToPast` are ignored.
If `startFromCurrentCycle` is `false` (or not set), and `presentToFront` is `true`, then `presentToPast` is ignored.

**Note:** This endpoint requires an account token - an access token encoded with a Pismo account ID. Tokens can expire quickly, which can result in a **401 Unauthorized** message.

## Path parameters

- `accountId` integer, required

## Query parameters

- `statementId` integer
- `startCycle` integer
- `startFromCurrentCycle` boolean
- `presentToFront` boolean
- `presentToPast` boolean
- `beginDueDate` string, date
- `endDueDate` string, date
- `maxClosedCycles` integer
- `page` integer
- `perPage` integer

## Response `200`

Ok

- AccountStatementsListResponse
  - `items` AccountStatementsResponse[]
    - `statement_id` integer: Statement ID
    - `status` string: Statement status. The possible values are: * `CLOSED`: Statement is closed, and the due date has already passed. * `CLOSED_NOT_DUE`: Statement is closed, but the due date has not yet passed. In other words, the current date is between the statement's cycle closing date and due date. * `OPEN`: Statement is open. This is the current statement, before cycle closing. * `FUTURE`: Future statement. That is, a statement that has not been opened yet. Statements with this status usually include installments from purchases that will be due in future billing cycles.
    - `cycle` integer: Cycle number. When an account is created, its first cycle is cycle number 1. This number is incremented for each successive cycle.
    - `previous_balance` number, float: Amount you owed on the account when the previous statement closed.
    - `debits` number, float: Total debits for current cycle
    - `credits` number, float: Total credits for current cycle
    - `current_balance` number: Total amount you owe on the account right now. It updates as transactions post, so it can change many times during a billing cycle. `current_balance` = `previous_balance` + `debits` - `credits`.
    - `posted_date` string, date: Date posted. Format = yyyy-mm-dd.
    - `minimum_payment` number, float: Statement minimum payment
    - `amount_due` number, float: Amount due. Must be less than or equal to `current_balance` and greater than zero. It should be equal to `current_balance` at cycle closing. **Note:** This field only appears in closed statements and only if they were closed after 17 April 2025.
    - `amount_paid_until_due_date` number, float: Amount discharged on or before real due date by credit transactions that <i>are</i> considered payments transactions. <b>Notes:</b> - If you do not use the program parameter [PAYMENTS_TTS](doc:multivalue-parameters) to configure the payments transactions, the Pismo platform uses the following transaction types as defaults: [201, 244, 255, 276, 282, 320, 342, 701, 711, 721, 2224] - This field only appears in closed statements and only if they were closed after 17 April 2025.
    - `amount_paid_after_due_date` number, float: Amount discharged after real due date by credit transactions that <i>are</i> considered payments transactions. <b>Notes:</b> - If you do not use the program parameter [PAYMENTS_TTS](doc:multivalue-parameters) to configure the payments transactions, the Pismo platform uses the following transaction types as defaults: [201, 244, 255, 276, 282, 320, 342, 701, 711, 721, 2224] - This field only appears in closed statements and only if they were closed after 17 April 2025.
    - `other_credits_until_due_date` number, float: Amount discharged on or before real due date by credit transactions that <i>are not</i> considered payment transactions. <b>Notes:</b> - If you do not use the program parameter [PAYMENTS_TTS](doc:multivalue-parameters) to configure the payments transactions, the Pismo platform uses the following transaction types as defaults: [201, 244, 255, 276, 282, 320, 342, 701, 711, 721, 2224] - This field only appears in closed statements and only if they were closed after 17 April 2025.
    - `other_credits_after_due_date` number, float: Amount discharged after real due date by credit transactions that <i>are not</i> considered payment transactions. <b>Notes:</b> - If you do not use the program parameter [PAYMENTS_TTS](doc:multivalue-parameters) to configure the payments transactions, the Pismo platform uses the following transaction types as defaults: [201, 244, 255, 276, 282, 320, 342, 701, 711, 721, 2224] - This field only appears in closed statements and only if they were closed after 17 April 2025.
    - `calendar` CalendarStatementsResponse
      - `calendar_id` integer: Calendar ID
      - `program_due_date_id` integer: Program due date ID
      - `program_id` integer: Program ID
      - `cycle_closing_date` string, date: Cycle closing date. Format = yyyy-mm-dd.
      - `due_date` string, date: Due date. Format = yyyy-mm-dd.
      - `real_due_date` string, date: Real due date. The regular due date does not take holidays into account. The real due date does, so it might be a later date. Format = yyyy-mm-dd.
    - `evolve_to_delinquency` boolean: Evolve to delinquency? If `false`, the account won't be updated to `OVERDUE`, and accruals won't be calculated. For some features like [Minimo Boleto](doc:calculating-interest-accruals#minimum-amount) and [transactions configured to not evolve delinquency](doc:configuring-transaction-types-to-not-accrue-charges), `OpenDueDate` is not filled at cycle closing with the next due date. So, even if he cardholder does not pay, the account's collection status is not changed to `OVERDUE`. In this case, the account is said to be set to "not evolve to delinquency".
  - `current_page` integer: Current page
  - `per_page` integer: Items per page
  - `total_items` integer: Number of items found
  - `items_on_page` integer: Number of items on this page
  - `pages` integer: Number of pages
  - `is_last_page` boolean: Is this the last page?

## Other responses

- `400`: Bad Request
- `500`: Internal Server Error

---

[API](https://skmtc.dev/pismo/apis/revolving-credit-statements.md) - [All operations](https://skmtc.dev/pismo/apis/revolving-credit-statements/llms.txt) - [OpenAPI document](https://skmtc.dev/pismo/apis/revolving-credit-statements/revisions/09f552b0f850?raw)