Skip to main content
PUT
Update access key status

gRPC method: UpdateAccessKeyStatus

Sets every access key for principalName to ACTIVE or SUSPENDED. Suspending a key prevents it from being used to authenticate without revoking it; reactivating it restores its usability.
data.json
Example request

Authorizations

Authorization
string
header
default:Bearer {API_ACCESS_TOKEN}
required

CoreWeave API access token sent as a bearer token in the Authorization header (the value is prefixed with Bearer). Used by every operation except the SAML/OIDC token-exchange endpoints (anonymous) and the container credentials GET (which uses ContainerCredentialsAuth).

Body

application/json

Inputs for updating the status of every access key owned by a principal.

principalName
string
required

The fully-qualified principal whose access-key status should change.

status
enum<string>
required

The new status to apply to every access key for the principal. ACTIVE makes the keys usable; SUSPENDED prevents authentication without revoking them. The underlying enum also declares INVALID (its zero value), which is never valid to send.

Available options:
ACTIVE,
SUSPENDED

Response

Last modified on September 3, 2026