seq_num
timestamp
tail_offset
(the number of records before the tail)
append
has received an acknowledgment before the read
request is made, the response will reflect the write.count
or bytes
size, or until
a specific timestamp.
ReadSession
(available via most SDKs) or using SSE, you are able to read in a streaming fashion. If a limit is not specified and the end of the stream is reached, the session goes into real-time tailing mode and will return records as they are appended to the stream.
SSE
Server push with Server-Sent-Events (SSE) is supported. Clients can request an SSE response by setting theAccept: text/event-stream
header.
Authorizations
Bearer authentication header of the form Bearer <token>
, where <token>
is your access token.
Headers
Defines the interpretation of record data (header name, header value, and body) with the JSON content type.
Use raw
(default) for efficient transmission and storage of Unicode data — storage will be in UTF-8.
Use base64
for safe transmission with efficient storage of binary data.
raw
, base64
Path Parameters
Stream name.
Query Parameters
Start from a sequence number.
x >= 0
Start from a timestamp.
x >= 0
Start from number of records before the next sequence number.
x >= 0
Limit total records to return. If this is provided, tailing will be disabled.
x >= 0
Limit total metered bytes to return. If this is provided, tailing will be disabled.
x >= 0
Exclusive timestamp to read until. If this is provided, tailing will be disabled.
x >= 0
Clamp the start position at the tail position. If set, the read will start at the tail of the stream if the requested position is greater than it.
Response
Records that are durably sequenced on the stream, retrieved based on the requested criteria. This can only be empty in response to a regular (non-SSE) read, if the request cannot be satisfied without violating an explicit limit.
Sequence number that will be assigned to the next record on the stream, and timestamp of the last record. This will only be present when reading recent records.