Fetch the next feed-event batch

Return events after the named consumer's server-held checkpoint. If the
consumer has no checkpoint, reading begins at the oldest event still
inside retention. Omitting consumer uses the default consumer.

Fetching is read-only. Repeating this request before acknowledgement can
return the same events. Process the complete batch, then send the response
cursor to the acknowledge endpoint with the same consumer name. The
next scheduled fetch does not need to retain or submit that cursor.

If a stored checkpoint has fallen outside retention, reading resumes at
the oldest retained event and retention.gap_detected is true. Session
events are webhook-only and are never returned.

Path Params
uuid
required

Feed UUID. The feed must belong to the authenticated workspace.

Query Params
string
length between 1 and 128
^[A-Za-z0-9][A-Za-z0-9._-]*$
Defaults to default

Name of the independent server-held checkpoint.

integer
1 to 1000
Defaults to 100

Maximum number of events to return.

Responses

Language
Credentials
Header
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json