Search Scope Role Bindings Per Catalog
Search scope-role bindings in a catalog, grouped by (app, scope) (one entry per scope with all role IDs aggregated). When app_id is provided the result is scoped to that app; when omitted the result spans every app in the catalog, ordered by (app_id, scope_id) so a client groupBy(app_id) produces contiguous app sections across page boundaries.
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.
Path Parameters
The unique identifier of the access profile.
Query Parameters
Optional: when set, restrict to a single app. When empty, span every app in the catalog.
The maximum number of results to return per page.
The token from a previous response's next_page_token, used to fetch the next page.
Optional substring search on the scope's app_resource display name (case-insensitive).
Optional filter on the scope's app resource type (for example, AWS Account).
Response
The response message containing the scope-role bindings in an access profile, one entry per (app, scope).
The response message containing the scope-role bindings in an access profile, one entry per (app, scope).
The list of scopes, each with its bound roles, ordered by app and then scope.
The nextPageToken is shown for the next page if the number of results is larger than the max page size. The server returns one page of results and the nextPageToken until all results are retrieved. To retrieve the next page, use the same request and append a pageToken field with the value of nextPageToken shown on the previous page.