Get Own Current Scope
const url = 'https://example.com/iam/v1/users/me/scope';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/scopeReturns the scope the caller works in: the most recent scope in their recent scopes they can still enter, otherwise the scope of their most recently granted role. Absent when they hold no organisation, workspace or group role.
Responses
Section titled “ Responses ”OK
Scope Selection
Where the caller works now. The scopes they worked in recently are listed by ListRecentScopes. Scopes are named by identifier only; resolve names from the organisation, workspace and group services.
object
The scope the caller works in now. Absent when the caller holds no organisation, workspace or group role they can enter.
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.
Example
{ "current_scope": { "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" } ]}