Page the event feed ascending from a (xact, seq) cursor

Events are served in (xact, seq) order and only once every transaction older than theirs has finished, so a consumer that stores the last event's (xact, seq) as its cursor sees every event exactly once, however long the writing transactions lived. The trade: delivery order follows transaction start, not commit, so a consumer must tolerate causally-later events (a pending's posted) arriving before earlier ones (its created). seq alone is NOT a safe cursor. When an old transaction pins the database-wide watermark the feed cannot advance, and an empty page would be a lie: that is refused as event_feed_blocked (503) instead of reported as caught up, so a stalled consumer retries rather than skipping events it was told did not exist. limit is clamped to the contract maximum.

Path Parameters

Query Parameters

Response Body