Azure DevOps REST API and Graph API: Pagination and Offset Support

Direct Answer

The Azure DevOps Graph API does not provide a documented alternative to $skip for non-sequential data access. Continuation-token traversal is the only supported pagination method for Graph API collection endpoints. There is no documented offset-based path that lets a client jump to a specific record without iterating through preceding pages.

Confirmed Behavior and Likely Explanation

Confirmed behavior

• Azure DevOps REST APIs page large result sets using the continuationToken query parameter.
• The server indicates additional pages through the x-ms-continuationtoken response header.
• The Graph API supports $top to limit page size on many collection endpoints.
• $skip is generally unsupported on Graph API collection endpoints and typically returns 400 Bad Request.
• Continuation tokens are opaque server-generated strings and cannot be manually calculated to simulate a numeric offset.

Likely explanation

Graph endpoints traverse relationships rather than scan flat tables, so the service may not maintain a stable ordinal position for records across requests. Implementing $skip would require materializing and numbering the full result set before applying the offset, which is expensive for graph traversals. The service therefore exposes continuation tokens as an opaque cursor instead of a skip count.

Verification Steps

1. Send a GET request to a Graph API collection endpoint with $top=10.
2. Inspect the response headers for x-ms-continuationtoken.
3. If present, pass that value as continuationToken in the next request to retrieve the following page.
4. Repeat until the header is absent, which indicates the final page.
5. Avoid $skip=10 in production calls; expect 400 Bad Request on most Graph API collection endpoints.

GET https://app.vssps.visualstudio.com/_apis/graph/...?api-version=7.0&$top=10
# Response header: x-ms-continuationtoken: OPAQUE_TOKEN

GET https://app.vssps.visualstudio.com/_apis/graph/...?api-version=7.0&$top=10&continuationToken=OPAQUE_TOKEN

Assumptions and Uncertainty

• This guidance applies to the Azure DevOps Graph API specifically; other Azure DevOps REST endpoints may use different paging mechanisms.
• Behavior can change between API versions. Pin the api-version parameter in your integration.
• Continuation tokens may expire or become invalid if the underlying data changes significantly between requests.
• Because current verification is required, confirm the 400 Bad Request behavior for $skip against your target endpoint before relying on it.

Missing Diagnostic Detail

Do you need random access to a specific record by position, or is sequential traversal acceptable? If you require true random access, the recommendation changes to fetching and caching pages client-side or filtering by a stable identifier rather than using an offset.