Report leaked credentials

If you find a Crane Ledger API key in a public place — an environment file, a git commit, a paste, logs, or a screenshot — do not use it. Submit it to the public burn endpoint so it is disabled immediately. You do not need an account.

This endpoint is modeled on GitHub’s unauthenticated POST /credentials/revoke. Crane Ledger burns API keys only. OAuth access and refresh tokens are ignored.

Do not use the key

Treat the secret as compromised. Do not call Crane Ledger APIs with it, do not add it to your own environment, and do not send it in an Authorization header. The burn endpoint rejects authenticated requests with 403.

Burn the key

Send the full secret string (not the key id) in a JSON array. You may include up to 1000 credentials per request.

POST/credentials/revoke
Auth required
curl -X POST "https://api.craneledger.ai/credentials/revoke" \
  -H "Content-Type: application/json" \
  -d '{"credentials":["ha_live_xxxxxxxxxxxxxxxxxxxxxxxx"]}'

Do not send an Authorization header.

What the response means

StatusMeaning
202 AcceptedThe request was well-formed. The body is an empty object {}. 202 does not confirm that a credential was valid, unknown, or already revoked.
403 ForbiddenThe request included authentication. This endpoint is for unauthenticated reporters only.
422 Unprocessable EntityMalformed JSON, missing credentials array, empty array, too many items, or non-string items.
429 Too Many RequestsUnauthenticated callers are limited to 60 requests per hour.

The response never says whether a submitted string was a real Crane Ledger API key.

What the owner sees

Crane Ledger does not email the key owner. If a submitted credential was an active API key, it is revoked immediately and the owner sees a notice in the API Keys dashboard after they sign in:

This key was auto-revoked by someone who discovered it. Please follow better security procedures. You can create a new API key above.

Owner-initiated revokes do not use that copy.

Scope

  • In scope: Crane Ledger API keys (ha_live_… / ha_test_…).
  • Out of scope: OAuth access tokens, refresh tokens, and anything that is not a Crane Ledger API key. Those strings still receive 202 and are not revoked.

For owner-managed key rotation and the authenticated DELETE /organizations/:organization_id/api-keys/:id path, see API Keys.


Need help?

Create a free account (GitHub, Google, Apple, or email) to access our support portal. Once signed in, use the Support tab in your dashboard to submit a support ticket — no GitHub account required. Our team typically responds within 24 hours.