Delete a secret

Revoke a credential. HARD — the row and the encrypted value both go. Deliberately NOT blocked when an environment still selects it: refusing would make a leaked credential un-revokable until someone edited every environment naming it, and revocation must never wait on cleanup.

DELETE /projects/{projectId}/secrets/{secretId}

Delete a secret

cURL

curl --request DELETE \
  --url https://app.mcpjam.com/api/v1/projects/{projectId}/secrets/{secretId} \
  --header 'Authorization: Bearer <token>'

200

Example

{ "id": "<string>", "projectId": "<string>", "name": "<string>", "deleted": true }

Authorizations

Authorization · string · header · required

MCPJam API key (sk_…). Create one at Settings → API keys. Guest sessions cannot use the API, and API keys cannot manage other API keys.

Path Parameters

projectId · string · required

ID of the hosted project that contains the server.

secretId · string · required

Secret ID, as returned by the project's secret list.

Response

200

application/json

The secret was revoked.

A HARD delete: the row and the encrypted value both go. This is the revoke button, so it is not soft.

id · string · required

projectId · string · required

name · string · required

Echoed so a caller logging the revoke needs no prior read.

deleted · enum<boolean> · required

Available options: true