SignaList<T> — a paginated response that supports three consumption patterns. The first page is fetched eagerly; subsequent pages are fetched lazily as you consume them.
Async Iteration
The simplest approach. Iterate across all pages automatically withfor await:
Collect to Array
Fetch all items into a single array withtoArray():
Manual Paging
For full control — inspect each page, access metadata, decide whether to continue:getNextPage() returns an empty list (not an error).
Page Properties
EverySignaList exposes:
| Property | Type | Description |
|---|---|---|
data | T[] | Items in the current page |
has_more | boolean | Whether more pages exist |
request_id | string | Unique request ID for debugging |
search_meta | SearchMeta? | Total count and timing (search responses only) |
aggregations | Record<string, Record<string, number>>? | Faceted counts (search responses only) |
Page Size
Control the number of items per page with thelimit parameter:
Search-Specific Metadata
Search responses include additional metadata not present on regular list responses:Cursor-Based
Signa uses cursor-based pagination (not offset-based). This means:- Results are stable even if new data is ingested between pages
- You cannot jump to an arbitrary page number
- Cursors are opaque strings — don’t parse or construct them