---
title: "List Transactions"
method: GET
path: "/transactions"
tags: ["Transaction"]
---

# List Transactions

`GET /transactions`

## Request

- Base URL: `https://api.orderful.com`
- URL: `https://api.orderful.com/transactions`
- Auth: API key in header `orderful-api-key`
- TypeScript: <https://skmtc.dev/orderful/apis/orderful-api/docs/transactions/get.ts> (a function with typed inputs; its response is checked against the schema)

Returns your organization's Transactions — inbound and outbound, across every trading relationship — sorted in descending order by their creation date. A maximum of 100 Transactions are returned per page; follow `metadata.pagination.links.next` to <a href="https://docs.orderful.com/reference/pagination" target="_blank">paginate</a> through the rest.

Every item carries ready-built `links` to the Transaction itself, its <a href="https://docs.orderful.com/reference/compositetransactioncontroller_getacknowledgment" target="_blank">acknowledgment</a>, and its <a href="https://docs.orderful.com/reference/transactionv4controller_getmessage" target="_blank">message content</a>, so you never need to assemble URLs from IDs.

## Query parameters

- `prevCursor` string
- `nextCursor` string
- `limit` integer
- `direction` string[]
- `businessNumber` string[]
- `validationStatus` string[]
- `deliveryStatus` string[]
- `acknowledgmentStatus` string[]
- `stream` string[]
- `ediTransactionType` string[]
- `simplifiedTransactionType` string[]
- `senderId` string[]
- `receiverId` string[]
- `createdAtStart` string
- `createdAtEnd` string

## Headers

- `orderful-api-key` string, required
- `orderful-api-version` string, required

## Response `200`

List of transactions, newest first.

- ListTransactionsV4ResponseDto
  - `metadata` ListTransactionsV4ResponseMetadataDto, required
    - `pagination` PaginationV3, required
      - `links` PaginationLinkV3, required
        - `next` string, nullable, required: Next URL which you can use to fetch the next page.
        - `prev` string, nullable, required: Previous URL which you can use to fetch the previous page.
  - `data` TransactionV4Dto[], required: The Transactions on this page, newest first.
    - `id` string, uuid, required: The Transaction's unique ID. This is the same value delivered as `id` in an inbound delivery payload, and the value the v4 transaction endpoints take as their path parameter.
    - `direction` 'in' | 'out', required: Whether the transaction was received (`in`) or sent (`out`) by your organization.
    - `senderId` string, required: ISA ID of the party that sent the transaction.
    - `receiverId` string, required: ISA ID of the party that received the transaction.
    - `ediTransactionType` string, required: The full Orderful transaction type identifier, for example `850_PURCHASE_ORDER` or the EDIFACT `ORDERS_PURCHASE_ORDER`. See <a href="https://docs.orderful.com/reference/available-transaction-types" target="_blank">Available Transaction Types</a>.
    - `simplifiedTransactionType` 'PURCHASE_ORDER' | 'PURCHASE_ORDER_ACKNOWLEDGMENT' | 'PURCHASE_ORDER_CHANGE' | 'SHIP_NOTICE' | 'INVOICE' | 'INVENTORY_ADVICE' | 'PRICE_SALES_CATALOG' | 'WAREHOUSE_SHIPPING_ORDER' | 'WAREHOUSE_SHIPPING_ADVICE' | 'WAREHOUSE_STOCK_TRANSFER_SHIPMENT' | 'WAREHOUSE_STOCK_TRANSFER_RECEIPT', nullable, required: Business name shared by every EDI transaction type that carries the same document, for example `INVOICE` for both `810_INVOICE` and `INVOIC_INVOICE`. `null` for any transaction type that has no alias — check for `null` rather than assuming a value is present. For the full mapping, see <a href="https://docs.orderful.com/reference/mosaic-schemas" target="_blank">Mosaic Schemas</a>.
    - `stream` 'test' | 'live', required: Whether the transaction belongs to the test or the live stream.
    - `validationStatus` 'PROCESSING' | 'VALID' | 'INVALID', required: Whether the transaction message passed guideline validation.
    - `deliveryStatus` 'PENDING' | 'SENT' | 'DELIVERED' | 'FAILED', required: How far the transaction has progressed towards its recipient.
    - `acknowledgmentStatus` 'NOT_ACKNOWLEDGED' | 'ACCEPTED' | 'REJECTED' | 'OVERDUE' | 'ACCEPTED_WITH_ERRORS', required: Whether the recipient has acknowledged the transaction.
    - `businessNumber` string, nullable, required: Identifier the document carries in your business, for example an invoice or purchase order number.
    - `createdAt` string, date-time, required: When the transaction was created.
    - `links` TransactionV4LinksDto, required
      - `self` string, uri, required: URL of this transaction resource.
      - `acknowledgment` string, uri, required: URL of this transaction's acknowledgment.
      - `message` string, uri, required: URL of this transaction's message content.

## Other responses

- `400`: A filter is invalid — an unknown enum value, more than 5 values where 5 is the maximum, a `limit` outside 1–100, or a timestamp that is not ISO 8601.
- `404`: The `orderful-api-version: v4` header is missing.

## Changes

- **2026-11-03** `fe0e82430746`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/orderful/apis/orderful-api/changes/transactions/get.md)

---

[API](https://skmtc.dev/orderful/apis/orderful-api.md) - [All operations](https://skmtc.dev/orderful/apis/orderful-api/llms.txt) - [OpenAPI document](https://skmtc.dev/orderful/apis/orderful-api/revisions/fe0e82430746?raw)