Search Graph
SearchGraph performs a server-side BFS traversal and returns a bounded, filtered subgraph. Exactly one of user_id, app_id, or resource_id must be set.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
This API uses OAuth2 with the Client Credential flow. Client Credentials must be sent in the BODY, not the headers. For an example of how to implement this, refer to the c1TokenSource.Token() function.
Body
SearchGraph request. Builds a filtered access graph starting from a root entity. Exactly one of user_id, app_id, or resource_id must be set. Server validates this constraint and returns InvalidArgument if violated.
The appId field.
Filters — all optional, applied at every traversal hop
The entitlementIds field.
The entitlementNameQuery field.
Traversal controls
Legacy per-parent fan-out limit. Superseded by max_nodes and server-computed per-parent budgets, but still honored for callers that set it.
Overall node budget for the returned subgraph. 0 uses the server default.
Legacy traversal page size. Superseded by max_nodes, but still honored for callers that set it.
Legacy pagination token. Superseded by max_nodes-based traversal, but still honored for callers that set it.
The resourceId field.
The resourceIds field.
The resourceNameQuery field.
The resourceTypeIds field.
Root entity — exactly one must be set
Response
SearchGraph response. Contains a subgraph of nodes and edges.
SearchGraph response. Contains a subgraph of nodes and edges.
The edges field.
The hasMore field.
True if the server-side node budget stopped the traversal before it finished walking the graph. Distinct from has_more, which can also be set by a request timeout or scan limit.
The nodes field.
The pageToken field.
The pathsReturned field.
The truncatedNodeIds field.