Get Permission
const url = 'https://example.com/iam/v1/permissions/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/permissions/exampleReturns a permission by its natural key (e.g. “compute.vm.create”)
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The natural key of the permission to retrieve (e.g. “compute.vm.create”)
Responses
Section titled “ Responses ”OK
Permission resource — a granular action that can be assigned to roles
object
The natural key of the permission (
The service this permission belongs to (e.g. “compute”)
The resource this permission applies to (e.g. “vm”)
The action this permission grants (e.g. “create”)
Human-readable explanation of the permission
Example generated
{ "name": "example"}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" } ]}