List Own Recent Scopes
const url = 'https://example.com/iam/v1/users/me/recent-scopes';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/iam/v1/users/me/recent-scopesLists the scopes the caller switched into and can still enter: at most ten, newest first, so the first entry is the current scope.
Parameters
Section titled “ Parameters ”Query Parameters
Section titled “Query Parameters ”The maximum number of entries to return. The service may return fewer than this value. If unspecified, at most 20 entries will be returned. The maximum value is 100; values above 100 will be coerced to 100. No more than ten recent scopes exist.
A page token received from a previous ListRecentScopes call.
AIP-160 filter expression.
Partial matches (:, a quoted wildcard, contains/startsWith/endsWith) ignore capitalisation; = and the relational operators are exact.
Filterable fields: scope_id, scope_type, visit_time.
AIP-132 order_by expression. Sortable fields: scope_type, visit_time.
AIP-158 offset mode: number of entries to skip. Mutually exclusive with
page_token; a request supplying both is an invalid request. Default 0.
Responses
Section titled “ Responses ”OK
ListRecentScopesResponse
Response message for ListRecentScopes.
object
The caller’s recent scopes, in switch order unless order_by was given.
Selected Scope
One scope in a scope selection.
object
The kind of scope: organisation, workspace or group. Never PLATFORM.
The scope’s identifier.
When the caller last switched into this scope. Absent when they never did: the scope of their most recently granted role, offered as a starting point.
A token to retrieve the next page, or empty when there are no more.
Exact count of entries matching the request’s filter, independent of paging.
Example
{ "recent_scopes": [ { "scope_type": "SCOPE_TYPE_UNSPECIFIED" } ]}default
Section titled “default ”Default error response
The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.
object
The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
A list of messages that carry the error details. There is a common set of message types for APIs to use.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.
object
The type of the serialized message.
Example generated
{ "code": 1, "message": "example", "details": [ { "@type": "example" } ]}