Pull events
Drain the agent’s durable event log past after. This is a plain pull: after is the last sequence you have processed, the page is everything newer, and nothing is acknowledged or consumed. A consumer that sees an event twice ignores it by event_id.
timeout greater than zero holds the request open until something arrives, up to thirty seconds. Persist the events and the new cursor together before advancing, and read has_more to know whether to pull again immediately.
Polling works alongside webhooks: both transports read one log, so an agent may run either or both.
Authorizations
Agent Token (rly_live_…), shown once when the agent is created.
Query Parameters
The highest sequence this consumer has processed. 0 starts from the beginning of the retained log. cursor is accepted as an alias.
x >= 0Seconds to hold the request open when no events are pending. 0 returns immediately with any pending events (nonblocking pull).
0 <= x <= 301 <= x <= 100Response
Events past the cursor, oldest first.
100The sequence of the last event on this page. Pass it as after on the next pull; it equals the request's after when the page is empty.
The highest sequence Relay has written to this agent's log.
True when next_cursor is behind latest, so another page is waiting.

