---
title: "GET /polling/transactions"
method: GET
path: "/polling/transactions"
---

# GET /polling/transactions

`GET /polling/transactions`

This endpoint is used to regularly poll for new transactions that have been processed in Core.

You must define one of `startDateTime` or `pageToken` when making a request.

You may optionally define a `pageSize`. The minimum `pageSize` is 1, and the maximum `pageSize` is 1000. The default is 100.

`startDateTime` takes a string in ISO 8601 format. (ex: `2023-08-10T18:00:00Z`). 
`startDateTime` must be set to at least 1 minute in the past.

The results will contain transactions that occurred after this `startDateTime`. Starting from the oldest to newest transactions ordered by the `processedAt` field. Note, this is _exclusive_ of the `startDateTime`, a transaction occuring at exactly `2023-08-10T18:00:00Z` for instance, would not be included. In addition, there is a 15 second window where newly created transactions will not be included to account for any network latency or clock drifts within the systems to ensure you do not miss any transactions.

Each request will _always_ return a `nextPageToken`, regardless of whether there are new transactions or not.

We DO NOT recommend trying to roll your own polling strategy leveraging `startDateTime` only. There are edge cases around two transactions occuring at the _exact_ same time and being on the edge of a pagination which could cause you to miss one due to the exclusive nature of `startDateTime`. We recommend using `pageToken`'s instead.

When making subsequent polling requests (not initiating with `startDateTime`), the `pageToken` can be used to continue iterating through pages of transactions. Usage of the `pageToken` guaruntees you will not miss any transactions on the stream. If at any point there are no more new transactions in the `item` array, you will still receive a `nextPageToken`. Continue to use this token to poll for new transactions. Once there are new transactions, they will be returned in the `item` array.

`pageToken`'s you have retrieved can serve as checkpoints. They do not expire, and you can always start from that point in the transaction stream again if you need to catch a system up or recover from a failure. Storing `pageToken`'s as part of your polling process is encouraged.

`pageToken`'s are unique per request, opaque, and should not be parsed or modified in any way. They are not guaranteed to be in any particular format, and may change in the future.

## Query parameters

- `pageSize` number — The maximum number of elements to return in a page. You can set this to a maximum of 500 elements. If not specified, the default is 100.
- `pageToken` string — A token returned by a previous call to this operation in the `nextPageToken`. If not specified, Stedi returns the first page of results.
- `startDateTime` string, date-time — An ISO 8601 formatted string. For example `2023-08-28T00:00:00Z`. Stedi returns transactions processed after this time.

## Response `200`

ListPollingTransactions 200 response

- ListPollingTransactionsResponseContent
  - `nextPageToken` string — The token used for pagination
  - `items` TransactionSummary[], required
    - `transactionId` string, required — A unique identifier for the processed transaction within Stedi. This ID is included in the [`transaction.processed.v2` event](https://www.stedi.com/docs/operate/event-types#transaction-processed), or you can retrieve it manually from the transaction's details page within the Stedi app.
    - `fileExecutionId` string, required
    - `status` 'failed' | 'succeeded', required
    - `direction` 'INBOUND' | 'OUTBOUND' | 'UNKNOWN', required
    - `mode` 'test' | 'production' | 'other', required
    - `processedAt` string, date-time, required
    - `artifacts` Artifact[], required
      - `artifactType` 'text/csv' | 'application/edifact' | 'application/filepart' | 'application/json' | 'application/pdf' | 'text/psv' | 'text/tsv' | 'application/edi-x12' | 'application/xml' | 'application/zip' | 'image/jpeg' | 'image/png' | 'image/tiff' | 'text/plain', required
      - `usage` 'attachment' | 'input' | 'metadata' | 'output', required
      - `sizeBytes` number, required
      - `url` string, required
      - `model` 'execution' | 'fragment' | 'transaction' | 'fault', required
    - `partnership` Partnership, required
      - `partnershipId` string, required — Identifier chosen by the user to uniquely identify a partnership.
      - `partnershipType` 'x12' | 'edifact', required
      - `sender` PartnershipSender, required
        - `profileId` string, required
      - `receiver` PartnershipReceiver, required
        - `profileId` string, required
    - `x12` X12TransactionSummary
      - `metadata` X12TransactionMetadata, required
        - `interchange` X12TransactionMetadataInterchange, required
          - `acknowledgmentRequestedCode` string, required
          - `controlNumber` number, required
        - `functionalGroup` X12TransactionMetadataFunctionalGroup, required
          - `controlNumber` number, required
          - `date` string, required
          - `functionalIdentifierCode` string, required
          - `time` string, required
          - `release` string, required
        - `transaction` X12TransactionMetadataTransaction, required
          - `controlNumber` string, required
          - `transactionSetIdentifier` string, required
        - `sender` X12TransactionMetadataProfile, required
          - `applicationCode` string, required
          - `isa` X12TransactionMetadataProfileISA, required
            - `qualifier` string, required
            - `id` string, required
        - `receiver` X12TransactionMetadataProfile, required
          - `applicationCode` string, required
          - `isa` X12TransactionMetadataProfileISA, required
            - `qualifier` string, required
            - `id` string, required
      - `transactionSetting` X12TransactionSetting
        - `guideId` string
        - `transactionSettingId` string
    - `fragments` TransactionFragmentsSummary
      - `keyName` string, required
      - `fragmentCount` number, required
      - `batchSize` number, required
    - `translationErrors` TranslationError[]
      - `context` TranslationErrorContext
        - `code` string
        - `schemaPath` string
      - `mark` Mark — The location in the document where the problem occurred. May be a single index or a range.
        - `start` Index, required
          - `line` number, required
          - `column` number, required
        - `end` Index
          - `line` number, required
          - `column` number, required
      - `message` string, required
    - `businessIdentifiers` BusinessIdentifier[]
      - `elementId` string, required — The identifier of the element as seen in the EDI ref.
      - `element` string, required — The element where the business identifier was found. For example, `BEG-03`.
      - `name` string, required — The friendly name of the business identifier. For example, `Purchase Order Number`.
      - `value` string, required
    - `operation` string

## Other responses

- `400` — ResourceUnderChangeException 400 response
- `401` — UnauthorizedException 401 response
- `403` — AccessDeniedException 403 response
- `404` — ResourceNotFoundException 404 response
- `429` — ThrottlingException 429 response
- `500` — ServiceException 500 response
- `503` — ServiceUnavailableException 503 response
- `504` — GatewayTimeoutException 504 response

## Changes

- **2025-04-22** `4446f4193c6b` — 5 warning
  - added the new `attachment` enum value to the `items/items/artifacts/items/usage` response property for the response status `200`
  - added the new `image/jpeg` enum value to the `items/items/artifacts/items/artifactType` response property for the response status `200`
  - added the new `image/png` enum value to the `items/items/artifacts/items/artifactType` response property for the response status `200`
  - added the new `image/tiff` enum value to the `items/items/artifacts/items/artifactType` response property for the response status `200`
  - …1 more
- **2025-02-26** `1aeee1accf92` — 1 info
  - added the optional property `items/items/operation` to the response with the `200` status
- **2025-02-05** `5cd01e1d1679` — 1 warning
  - added the new `fault` enum value to the `items/items/artifacts/items/model` response property for the response status `200`
- **2024-12-18** `6e04e598f826` — 3 info
  - the `items/items/partnership/partnershipId` response's property pattern was changed from `^([a-zA-Z0-9_-]+)$` to `^([a-zA-Z0-9._-]+)$` for the status `200`
  - the `items/items/partnership/receiver/profileId` response's property pattern was changed from `^([a-zA-Z0-9_-]+)$` to `^([a-zA-Z0-9._-]+)$` for the status `200`
  - the `items/items/partnership/sender/profileId` response's property pattern was changed from `^([a-zA-Z0-9_-]+)$` to `^([a-zA-Z0-9._-]+)$` for the status `200`

[Change history](https://skmtc.dev/stedi/apis/core/changes/polling/transactions/get.md)

---

[API](https://skmtc.dev/stedi/apis/core.md) · [All operations](https://skmtc.dev/stedi/apis/core/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/stedi/core/revisions/4446f4193c6b/schema)
