Poll transactions

Changed on

Stedi Core-compatible Poll Transactions. Returns transactions in ascending processing order so an incremental consumer can follow the stream without gaps.

Supply either startDateTime (initial poll) or pageToken (subsequent polls) — at least one is required. Unlike the list endpoint, polling always returns a nextPageToken, including on an empty page: when no new transactions are ready, the token re-encodes your current position rather than advancing the cursor, so no transaction can be skipped by a concurrent webhook or a delayed retry. Persist the token and pass it back on the next poll.

get/api/stedi/2023-08-01/polling/transactions

Request

  • Base URL
    https://forecaster.cairhealth.com
  • URL
    https://forecaster.cairhealth.com/api/stedi/2023-08-01/polling/transactions
  • Auth
    HTTP bearer

Query parameters

pageSizeinteger

Maximum number of transactions to return in a page (1–500). Defaults to 100.

pageTokenstring

Cursor returned as nextPageToken by the previous poll. Pass this on every poll after the first. Mutually exclusive with startDateTime (the token wins).

startDateTimestring date-time

ISO 8601 date-time for the initial poll, e.g. 2026-10-01T00:00:00Z. Only transactions after this time are returned. Required on the first poll when no pageToken is available.

Response

A page of new transactions. nextPageToken is always present.

nextPageTokenstring required

Always present. Pass it back on the next poll. On an empty page it encodes your current position so no transactions are skipped.

Changes