Delete a secret

⚠️
Preview — this feature is being built; the design below is the spec.
DELETE https://app.syntic.ai/v1/vaults/{vault_id}/secrets/{name}

Delete one secret. Tools that refer to it by name fail from then on with a tool error the agent can see.

For how this fits into a full workflow, see Credential vaults.

Headers

HeaderRequiredValue
AuthorizationYesBearer <key>: a private inference key (sk_live_...). See Authentication.
syntic-betaYes, while in previewagents-2026-11-01. Without it the call fails with 400 beta_required. See Versioning.

Path parameters

ParameterTypeDescription
vault_idstringThe vault id, starting with vlt_.
namestringThe secret’s name.

Response

200 OK, Content-Type: application/json

{
  "vault_id": "vlt_01JC2B4D6F8H0K2M4P6R",
  "name": "crm-token",
  "deleted": true
}

Examples

curl -sS -X DELETE https://app.syntic.ai/v1/vaults/vlt_01JC2B4D6F8H0K2M4P6R/secrets/crm-token \
  -H "Authorization: Bearer $SYNTIC_API_KEY" \
  -H "syntic-beta: agents-2026-11-01"

Errors

Errors use the error envelope and carry a request_id. Codes specific to this operation:

StatustypecodeWhen
400invalid_request_errorbeta_requiredThe syntic-beta header is missing.
403permission_errorrole_requiredThe key’s creator is not an Administrator or Owner.
404not_found_errorvault_not_foundNo vault with that id in this workspace.
404not_found_errorsecret_not_foundThe vault has no secret with that name.
401authentication_errorinvalid_api_keyThe key is missing, unknown, revoked or expired.
429rate_limit_errorrate_limitedToo many requests; wait for Retry-After. See Rate-limit headers.

Who may call this

Creating vaults and writing or deleting secrets needs a key created by an Administrator or Owner. Any key in the workspace may list vaults and read secret names, so developers can wire up agents without ever handling values.

Was this page helpful?