Skip to main content
List operations return results in pages. Most use page-number pagination; operations over large or fast-changing collections also accept a cursor. The parameters an operation supports, and their limits and defaults, are documented on its page — the values below are the common defaults, not guarantees for every operation.

Page-number pagination

Request parameters

Response fields

Example

Depth limit

On On-call list operations, p × limit must be at most 10,000. Deeper pages fail with 400 InvalidParameter. To walk further, use cursor pagination where the operation supports it, or narrow the filters (for example, a shorter time range).
Page-number pagination can skip or repeat items when objects are created or deleted between two calls, because offsets shift. Use a cursor for complete, stable exports.

Cursor pagination

Pass search_after_ctx from the previous response to get the next page. A cursor is opaque: do not build or modify it, and keep the other request parameters unchanged between pages. When search_after_ctx is set, p is ignored. On List incidents and List alerts you can start with page-number pagination and switch at any time: every non-empty page also returns search_after_ctx, the cursor after its last item.

Request parameters

Response fields

Example

Operations that accept search_after_ctx

A few operations use other styles, documented on their pages: List work items takes a cursor, and some AI SRE and monitors lists take an offset.

About total

total is not always exact. To keep large queries fast, operations over incidents, alerts, alert events, post-mortems, and mapping data stop counting at 1,000:
  • When fewer than 1,000 items match, total is exact.
  • When 1,000 or more match, total is 1,000, meaning “1,000 or more”.
Use has_next_page, not total, to decide whether to fetch another page: has_next_page does not depend on total and stays accurate past 1,000 items.