---
title: "List transactions (transaction banking)"
method: GET
path: "/corporate/v1/corporate-transactions"
tags: ["Transactions"]
---

# List transactions (transaction banking)

`GET /corporate/v1/corporate-transactions`

## Request

- Base URL: `https://sandbox.pismolabs.io`
- URL: `https://sandbox.pismolabs.io/corporate/v1/corporate-transactions`
- Auth: HTTP bearer

Lists transactions of your transaction banking account.

## Query parameters

- `offset` integer
- `limit` integer
- `statementId` integer
- `customerId` integer
- `transactionTypeId` integer
- `processingCode` string
- `credit` boolean
- `statementPost` boolean
- `authorizationId` integer
- `authorizationType` 'PLATFORM' | 'NETWORK'
- `eventDateStart` string, date-time
- `eventDateEnd` string, date-time
- `order` 'asc' | 'desc'
- `authorizationTrackingId` string
- `ids` integer[]
- `userCategory` string
- `paymentMethodId` string
- `numberOfLatestTransactions` integer

## Response `200`

OK

- ListTransactionsResponse
  - `transactions` TransactionResponse[]: List of transactions
    - `id` integer: Transaction ID
    - `program_id` integer: Program ID. This is a client-provided ID.
    - `account_id` integer: Account ID
    - `external_account_id` string: Custom account ID. Used as the key for all operations (manage accounts, transactions, etc.) on the corporate layer. This field is: - Unique within the Organization - Immutable: The field cannot be updated. - Not recyclable: You can't reuse an external account ID, even if the account that was using it has been canceled.
    - `soft_descriptor` string: Brief description that helps to identify a particular transaction on the bank statement.
    - `processing_code` string: Processing code used to create the underlying transaction. Each internal operation type uses a default processing code.<br> `minLength: 1` `maxLength: 6`
    - `processing_description` string: Processing code description
    - `amount` Amount: Amount
      - `value` number, float, required: Amount value
      - `currency` string: 3-letter code in ISO 4217-compliant format for the currency used in the transaction.
    - `event_date` string, date-time: Event date in format ISO 8601.
    - `payment_date` string, date-time: Date and time of the payment. Specifying a `payment_datetime` value impacts the account balance history.<br> <b>Notes</b>: - The payment datetime is in ISO 8601 format. - You can backdate payments a maximum of 390 calendar days. You can postdate payments a maximum of 10 calendar days.
    - `created_at` string, date-time: Transaction creation date in format ISO 8601
    - `transaction_type` TransactionType: Transaction type
      - `id` integer: Transaction type ID
      - `description` string: Transaction type description
      - `credit` boolean: Is the transaction a credit (`true`) or debit (`false`)?
      - `posted_transaction` boolean: Are transactions posted on statements?
    - `authorization` Authorization: Authorization
      - `id` integer: Authorization ID
      - `type` 'PLATFORM' | 'NETWORK': Authorization type
      - `code` string: Authorization code or network approval code
      - `payment_method_id` string: Payment method
      - `tracking_id` string: A unique payment tracking number provided by the client. If an existing `tracking_id` is found on the Pismo platform, the API returns a `409` error. This field is: * Unique within the organization * Immutable: It can't be updated * Not recyclable: You can't reuse a `tracking_id`
    - `metadata` Metadata: Key-value pairs that contain data intended for storage on the Pismo platform.<br> **Note**: The `metadata` field includes a `corporate_metadata` object with the following attributes: * `credit_external_account_id`: present when supplied in the credit leg. * `debit_external_account_id`: present when supplied in the debit leg. * `earmark_id`: present when supplied in the debit leg. The `corporate_metadata` attribute must be an object. A type mismatch results in an error as described in the responses section.<br> **Note**: This field must not be used to send Personally Identifiable Information (PII), Payment Card Industry (PCI) data, or any sensitive/regulated information. Metadata fields are intended for operational, non-sensitive data only. For sensitive data, use the specific parameters designed for that purpose. For more information, refer to [Get started with Pismo APIs](ref:get-started-with-pismo-apis#metadata).
  - `pagination` OffsetPagination: Data related to list pagination using an offset parameter
    - `has_next` boolean: Whether there are more pages after the current page (`true`) or not (`false`).
    - `limit` integer: Maximum number of items per page
    - `offset` integer: Starting index of the result list. Default is 0.

## Other responses

- `400`: A Bad Request validation error
- `401`: Unauthorized.
- `403`: Forbidden
- `500`: Internal Server Error

---

[API](https://skmtc.dev/pismo/apis/banking-transaction-banking.md) - [All operations](https://skmtc.dev/pismo/apis/banking-transaction-banking/llms.txt) - [OpenAPI document](https://skmtc.dev/pismo/apis/banking-transaction-banking/revisions/1334306c9303?raw)