---
title: "List by Page (deprecated)"
method: GET
path: "/transactions"
tags: ["Transaction"]
deprecated: true
---

# List by Page (deprecated)

`GET /transactions`

> **Deprecated.**

**Deprecated**: this endpoint is deprecated and will be available only until **2026-12-31**, after which it will be removed. Please migrate to `GET /v2/transactions`, which uses cursor-based pagination.

Recovers all transactions collected for the acount provided.

## Query parameters

- `accountId` string, uuid, required
- `ids` string[]
- `from` string, date-time
- `to` string, date-time
- `pageSize` number, double
- `page` number, double
- `billId` string, uuid
- `createdAtFrom` string, date-time

## Response `200`

Retrieve a list of all transactions for an account

- PageResponseTransactions
  - `results` Transaction[], required
    - `id` string, required — Primary identifier of the transaction
    - `description` string, required — Clean description of the transaction
    - `descriptionRaw` string, nullable — Original transaction description as returned by the institution, before any cleanup or normalization. May be null when not provided by the institution.
    - `currencyCode` string, required — Currency ISO code
    - `amount` number, double, required — Transaction amount
    - `amountInAccountCurrency` number, double — Transaction amount in Account's Currency. Only present if the transaction is in a different currency than the account's currency
    - `date` string, date-time, required — Date when the transaction was made
    - `type` 'DEBIT' | 'CREDIT' — Direction of the movement from the account holder's perspective. - `CREDIT`: money entered the account (deposits, incoming transfers, refunds). - `DEBIT`: money left the account (payments, withdrawals, outgoing transfers, credit-card purchases). Note: for credit-card accounts the convention is inverted at the institution but Pluggy normalizes the value so purchases are always `DEBIT` and payments to the card statement are `CREDIT`.
    - `balance` number, double — Account balance immediately after the transaction was posted. May be null when the institution does not return a running balance.
    - `providerCode` string — Institution-provided identifier or code for the transaction (e.g. NSU, transaction number on the bank statement). Format varies per institution.
    - `status` 'POSTED' | 'PENDING' — Settlement status of the movement. - `POSTED`: the transaction is confirmed/settled at the institution. - `PENDING`: the transaction is authorized but not yet settled (typical for credit-card purchases not yet included in a closed bill).
    - `category` string — Category of the transaction (e.g. Restaurants, Education). See the Transaction Categorization section in our guides.
    - `categoryId` string — Id of the transaction category. Can be used to identify the category in the Categories endpoint
    - `paymentData` PaymentData — Payment or Transfer participant's data
      - `payer` PaymentDataParticipant — Participant of the payment data
        - `documentNumber` Document — Document object containing type & value
          - `type` 'CPF' | 'CNPJ' — Type of document
          - `value` string — Formatted value of the document
        - `name` string — Fullname of the participant
        - `accountNumber` string — Account number on the branch
        - `branchNumber` string — Agency number
        - `routingNumber` string — COMPE Bank number
        - `routingNumberISPB` string — ISPB Bank number
      - `receiver` PaymentDataParticipant — Participant of the payment data
        - `documentNumber` Document — Document object containing type & value
          - `type` 'CPF' | 'CNPJ' — Type of document
          - `value` string — Formatted value of the document
        - `name` string — Fullname of the participant
        - `accountNumber` string — Account number on the branch
        - `branchNumber` string — Agency number
        - `routingNumber` string — COMPE Bank number
        - `routingNumberISPB` string — ISPB Bank number
      - `reason` string — User's motive submitted while making the transfer
      - `referenceNumber` string — Reference number for the transfer/payment
      - `receiverReferenceId` string — String submitted by the receiver associated with the payment when generating the payment request.
      - `authenticationCode` string — Authentication code of the payment receipt, as printed by the institution on the proof of payment. It identifies the operation itself rather than the payment instrument, so it can be present for any payment method (PIX, TED, DOC, BOLETO).
      - `paymentMethod` string — Payment rail used for the transaction. - `PIX`: instant transfer over the Brazilian Pix system. - `TED`: Transferência Eletrônica Disponível (same-day inter-bank transfer). - `DOC`: Documento de Ordem de Crédito (D+1 inter-bank transfer, deprecated by the Central Bank). - `TEV`: Transferência Eletrônica de Valores (intra-bank transfer between accounts of the same institution). - `BOLETO`: Brazilian bank slip payment.
      - `boletoMetadata` PaymentDataBoletoMetadata — Information of the boleto associated with the payment
        - `digitableLine` string — Boleto identifier
        - `barcode` string — Boleto barcode number
        - `baseAmount` number — Boleto original amount without considering penalties / interests / discounts
        - `interestAmount` number — Boleto interest amount
        - `penaltyAmount` number — Boleto penalty amount
        - `discountAmount` number — Boleto discount amount
    - `creditCardMetadata` CreditCardMetadata — Data of a transaction specific to credit card transactions
      - `installmentNumber` number — Number of the current installment of the purchase
      - `totalInstallments` number — Total number of installments of the purchase
      - `totalAmount` number — Total amount of the purchase
      - `feeType` 'ANNUAL_FEE' | 'ATM_WITHDRAWAL_DOMESTIC' | 'ATM_WITHDRAWAL_INTERNATIONAL' | 'EMERGENCY_CREDIT_EVALUATION' | 'CARD_REISSUE' | 'BILL_PAYMENT_FEE' | 'SMS' | 'OTHER' — Type of fee charged. Present when the operation is a fee (TARIFA)
      - `feeTypeAdditionalInfo` string — Free text describing the fee type when feeType is 'OTHER'
      - `otherCreditsType` 'REVOLVING_CREDIT' | 'BILL_INSTALLMENT' | 'LOAN' | 'OTHER' — Other type of credit contracted on the card. Present when the operation is a contracted credit operation
      - `otherCreditsAdditionalInfo` string — Free text describing the other credit type when otherCreditsType is 'OTHER'
      - `purchaseDate` string, date-time — Original Date of the purchase
      - `payeeMCC` string — Merchant Category Code of the merchant
      - `cardNumber` string — Credit Card Number associated with transaction, can be different from the account if its done by an additional or virtual card.
      - `billId` string — Id of the bill associated to this transaction
      - `billForecastDate` string — Forecasted bill period (formatted as YYYY-MM) in which this transaction is expected to be charged. Unlike billId, it is provided for pending and future transactions too. Only returned for Open Finance connectors
    - `merchant` Merchant — Merchant extracted from the transaction data
      - `name` string — Merchants name
      - `businessName` string — Merchant legal business name
      - `cnpj` string — Document number related to the merchant
      - `cnae` string — Economic activity classification number related to the merchant
    - `operationType` string, nullable — Type of operation classified by the institution. Only returned for Open Finance connectors.
    - `operationTypeAdditionalInfo` string, nullable — Complementary, free-form information about the operation type, as provided by the institution. Varies by institution (a sub-type code or a description). Only returned for Open Finance connectors.
    - `providerId` string — Provider's identifier for the transaction. Only returned for Open Finance connectors.
    - `accountId` string, uuid, required — Identifier of the account this transaction belongs to.
    - `order` number — Sequential position of the transaction within the same day, used to preserve ordering when multiple transactions share the same date.
    - `createdAt` string, date-time, required — Date when the transaction was first ingested by Pluggy.
    - `updatedAt` string, date-time, required — Date of the last update of the transaction data.
  - `page` number, double, required
  - `total` number, double, required
  - `totalPages` number, double, required

## Other responses

- `400` — Missing parameter
- `500` — Server Internal Error

---

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