Get IAM Binding
const url = 'https://example.com/iam/v1/bindings/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/bindings/exampleReturns an IAM binding by unique ID
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The unique identifier of the IAM binding to retrieve
Responses
Section titled “ Responses ”OK
IamBinding resource — links a principal to a role within a scope, optionally constrained by a policy
object
The unique identifier of the binding
The ID of the principal (user) this binding applies to
The type of principal
The role granted by this binding
The type of scope this binding applies to
The ID of the scoped resource (workspace, group, or organisation)
Optional policy that constrains when this binding is effective
Created Timestamp
The timestamp when the binding was created
Updated Timestamp
Timestamp when the IamBinding was last updated
Example
{ "principal_type": "PRINCIPAL_TYPE_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" } ]}