Delete a secret

POST 
/api/v1/secrets/delete

Deletes the stored value before its metadata. An absent secret is an idempotent success with deleted false, which may be omitted. A failure does not prove the previous value remains intact.

Known custom MCP references block deletion with 409 unless force is used. Detach or rebind those consumers first where possible. The reference list covers tracked custom servers, not every possible external consumer. Forced deletion can break future credential resolution; it does not recall cached or already dispatched use, revoke the credential at its issuer, or attest to backup erasure.

The following access conditions are preserved as declared intent and are not implemented by generated code: Authorized tenant project secret administration.

Use this in a guide: Connect a private tool without putting its credential in prompts · Answer questions about a website using your own Firecrawl account · Secret values and credential references

Request

Responses

200

Delete processed

Use the name of an existing secret in the authenticated project.

Section ID: DOC-CP-secrets-api-deleteSecret#example-secrets-deleteSecret-request

Request example

{
  "name": "travel-provider-api-key"
}

Illustrative response shape; omitted default fields and actual outcomes depend on the operation.

Section ID: DOC-CP-secrets-api-deleteSecret#example-secrets-deleteSecret-response

Response example

{
  "deleted": true
}

Document ID: DOC-CP-secrets-api-deleteSecret. Section identities and revisions.

Section	Stable reference
Delete a secret	DOC-CP-secrets-api-deleteSecret#overview
Request	DOC-CP-secrets-api-deleteSecret#request
Responses	DOC-CP-secrets-api-deleteSecret#responses