Get Role
const url = 'https://example.com/iam/v1/roles/example';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/roles/exampleReturns a role by unique ID
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The unique identifier of the role to retrieve
Responses
Section titled “ Responses ”OK
Role resource — a named collection of permissions assignable to principals
object
The unique identifier of the role
The display name of the role
An optional description of the role
The type of role (system or custom)
The lifecycle stage of the role
The type of scope this role is defined in (only for custom roles)
The ID of the scoped resource (only for custom roles)
Created Timestamp
The timestamp when the role was created
Updated Timestamp
Timestamp when the Role was last updated
Example
{ "role_type": "ROLE_TYPE_UNSPECIFIED", "stage": "ROLE_STAGE_UNSPECIFIED", "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" } ]}