Skip to main content
PUT
/
v1
/
cwobject
/
access-key-status
Update access key status
curl --request PUT \
  --url https://api.coreweave.com/v1/cwobject/access-key-status \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "principalName": "<string>"
}
'
This response has no body data.

​
gRPC method: UpdateAccessKeyStatus

Sets every access key for principalName to ACCESS_KEY_STATUS_ACTIVE or ACCESS_KEY_STATUS_SUSPENDED. Suspending a key prevents it from being used to authenticate without revoking it; reactivating it restores its usability.
data.json
{
  "principalName": "coreweave/ueqXfgRCYGqptEXAMPLE1",
  "status": "ACCESS_KEY_STATUS_SUSPENDED"
}
Example request
curl -X PUT https://api.coreweave.com/v1/cwobject/access-key-status \
       -H "Content-Type: application/json" \
       -H "Authorization: Bearer {API_ACCESS_TOKEN}" \
       -d @data.json

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. ACCESS_KEY_STATUS_ACTIVE makes the keys usable; ACCESS_KEY_STATUS_SUSPENDED prevents authentication without revoking them.

Available options:
ACCESS_KEY_STATUS_ACTIVE,
ACCESS_KEY_STATUS_SUSPENDED

Response

Last modified on June 25, 2026