Read
At the simplest level, you can read a batch of records with a single call:- TypeScript
- Go
- Rust
Navigating a stream
Every record in a stream is accessible by its sequence number, timestamp, or offset from the current tail. This is the case for both unary and streaming reads. Streaming reads that do not specify a stop condition will continue to follow updates in real-time.Starting from a sequence number
- TypeScript
- Go
- Rust
Starting from a tail offset
Read the last N records in the stream, then follow for new ones:- TypeScript
- Go
- Rust
Starting from a timestamp
Read records starting from a point in time:- TypeScript
- Go
- Rust
Reading until a timestamp
Read records up to a point in time, then stop:- TypeScript
- Go
- Rust
Read Session
A read session streams records from a starting position. It handles reconnection on transient failures and provides a simple iterator interface.Following live updates
By default, a read session without stop conditions will follow the stream indefinitely, waiting for new records as they arrive. When you provide a stop condition (count, bytes, or until), the read stops when either the condition is met or it reaches the current tail—whichever comes first.
See follow live updates in the API docs for the full semantics.
Long polling
Thewait parameter controls how long to wait for new records when caught up to the tail. This works for both unary reads (long polling) and sessions.
- TypeScript
- Go
- Rust
Check Tail
To find the current end of the stream without reading any records:- TypeScript
- Go
- Rust

