When you need more than a single transaction, retrieve every transaction that matches a set of criteria with the List Transactions API. It's a filtered, paginated search: you pass filter conditions (which accounts, which dates, which method or status) and PCE returns the matching transactions, newest-first.

Use it to build a transaction history, reconcile a date range, or find every transaction tied to an account, a payee, or your own externalId, without polling each transaction by ID.

List transactions

Make POST request to /v1/transaction/list. Like other Treasury calls, it requires the PromiseMode header (NEVER for an immediate response, ALWAYS to defer processing).

Request

POST /v1/transaction/list
PromiseMode: NEVER

{
  "pageNumber": 1,
  "pageSize": 25,
  "getTotalCount": true,
  "sortOptions": {
    "sortBy": "lastUpdatedOn",
    "sortOrder": "DESC"
  },
  "criteria": {
    "filters": [
      { "operator": "eq",  "key": "source.account.id", "values": [4000693] },
      { "operator": "gte", "key": "createdOn",         "values": ["07/15/2024 00:00:00"] }
    ]
  }
}

Response

{
  "totalCount": 1,
  "returnedCount": 1,
  "pageNumber": 1,
  "offset": 230001518,
  "hasMore": false,
  "resources": [
    {
      "resourceName": "transaction",
      "url": "/v1/transaction/id/230001518",
      "id": 230001518,
      "amount": "5.00",
      "type": "REGULAR",
      "method": "WIRE",
      "purpose": "payment",
      "transactionClass": "SEND",
      "source": {
        "account": {
          "resourceName": "account",
          "url": "/v1/customer/id/4000854/account/id/4000693",
          "id": 4000693
        }
      },
      "destination": {
        "externalAccount": {
          "id": 4021251,
          "accountNumberLast4": "2309",
          "routingNumber": "011000015",
          "holderName": "Lola",
          "holderType": "CORPORATE",
          "status": "ACTIVE"
        }
      },
      "scheduleDate": "07/16/2024",
      "status": "SCHEDULED",
      "statusReason": "On User Request",
      "statusDate": "07/16/2024 07:01:28",
      "createdOn": "07/16/2024 07:01:28",
      "lastUpdatedOn": "07/16/2024 07:01:28"
    }
  ]
}

Filters

Pass one or more filter conditions in criteria.filters[]. Each condition is a key, an operator, and one or more values. criteria is required.

Supported operators: eq, ne, gt, gte, lt, lte, in, nin, like.

Pagination & sorting

A criteria match can span many transactions; page through the result set rather than pulling everything at once.

The response echoes totalCount, returnedCount, pageNumber, offset (the ID of the last record returned), and hasMore so you can request the next page.

Scenarios

List transactions for an account

Read every transaction that moved money from one account, newest-first, the backbone of an activity view.

• Filter on source.account.id (or destination.account.id) with eq.
• Sort lastUpdatedOn DESC, set a modest pageSize, and page as the customer scrolls.

Reconcile a date range

Pull everything created in a window to reconcile against your own records.

• Combine createdOn gte (start) and createdOn lte (end).
• Add getTotalCount: true so you know how many transactions to expect across pages.

Find failed or pending transactions

Surface transactions that need attention.

• Filter status in ["PENDING", "FAILED"].
• Add a method filter (for example eq ACH) to narrow to one rail.

Find ACH reversals

Locate reversals generated against your ACH transactions.

• Filter type in ["REVERSAL"]. Each reversal's processingDetail.parent links back to the original transaction.

Best practices

See also

• Transaction lifecycle: statuses, tracking a single transaction, and the payment-methods directory
• Find & track recurring transactions: list recurring schedules and the transactions they generate
• Account ledger & activity: posted debits and credits with the running balance
• Error Codes and Messages: reason and return codes when a transaction fails