Visibility: public · internal ( OpenAPI Custom Extension: x-visibility )
Retrieve metadata for a single service account. Only tenant administrators can access this endpoint. Non-admin callers receive 404 to prevent resource enumeration.
Bearer token authentication using OAuth2/OIDC tokens
Service account resource identifier.
Service account metadata.
Service account for machine-to-machine and infrastructure access. Service accounts are independent principals with their own identity and role bindings. They are scoped to a level in the resource hierarchy (organization, or project) and survive the off-boarding of the user who created them.
Authentication uses client_id (on this resource) combined with a client_secret (from a credential sub-resource) via the grant_type=client_credentials flow.
Only tenant administrators can create and manage service accounts.
Server-generated UUID. Immutable.
Human-readable display name for the service account.
1 - 255"Production CI/CD Pipeline"
Unique client identifier for OAuth2 client_credentials flow. Server-generated, immutable. Used together with a credential's client_secret to authenticate at the token endpoint.
"sa-pipeline-prod@myorg.iam"
The level in the resource hierarchy this service account operates within:
Subject to org-level policy constraints.
organization, project "project"
Resource identifier corresponding to the scope level:
"proj-abc123"
Current service account status.
active, disabled "active"
User ID of the tenant administrator who created this service account.
"user-admin-001"
Timestamp when the service account was created.
Server-defined URL for this resource.
"/v1/iam/service-accounts/sa-pipeline-prod"
Optional description of the service account's purpose.
1024Role bindings assigned directly to this service account. Unlike API keys, service account roles are not inherited from a user — they are explicitly granted. Each role must be a valid org-defined role slug.
The assigning administrator can only grant roles they themselves hold within the service account's scope (scope-down principle). Effective privileges are bounded by the scope.
["compute.deployer", "storage.writer"]Timestamp of the last metadata change.
Number of active (non-expired) credentials on this service account. Maximum of 5 credentials allowed.
2