DELETE
/
v1
/
private-locations
/
{id}
/
keys
/
{keyId}
Remove an existing API key for a private location
curl --request DELETE \
  --url https://api.checklyhq.com/v1/private-locations/{id}/keys/{keyId} \
  --header 'Authorization: <api-key>'
This response does not have an example.

​
Overview

The Delete Private Location Key endpoint permanently removes an API key from a private location. This action immediately invalidates the key and stops authentication for any agents using it. Common Use Cases:
  • Key Rotation
  • Security Incident Response
  • Agent Decommissioning
  • Access Revocation
Deleting API keys immediately invalidates them and will cause authentication failures for agents using the deleted key. Ensure agents are updated with new keys before deletion.
Coordinate key deletion with agent updates to avoid monitoring interruptions. Have replacement keys ready before removing old ones.

Authorizations

​
Authorization
string
header
required

The Checkly Public API uses API keys to authenticate requests. You can get the API Key here.

Your API key is like a password: keep it secure!

Authentication to the API is performed using the Bearer auth method in the Authorization header and using the account ID.

For example, set Authorization header while using cURL:

curl -H "Authorization: Bearer [apiKey]" "X-Checkly-Account: [accountId]"

Headers

​
x-checkly-account
string

Your Checkly account ID, you can find it at https://app.checklyhq.com/settings/account/general

Path Parameters

​
id
string
required
​
keyId
string
required

Response

No Content