Delete a secret from Vault
const url = 'https://your-org.evershell.ai/v1/secrets/example';const options = {method: 'DELETE', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request DELETE \ --url https://your-org.evershell.ai/v1/secrets/example \ --header 'Authorization: Bearer <token>'Permissions: secrets:write.
The secret name is the path segment, not a body field.
Capabilities that reference the secret by secrets["name"]
will fail on their next call — the proxy logs
transforms_failed.<transform>: auth_unavailable on the
resulting deny.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Responses
Section titled “ Responses ”OK
object
Example
{ "status": "deleted"}Validation failure
object
object
Closed-enum slug (e.g. permission_denied, validation_error, workspace_not_found)
Human-readable summary
Server-generated request id for correlating logs
Optional structured context. Validation errors land at
details.fields as a per-field map.
object
Example
{ "error": { "code": "permission_denied", "message": "caller lacks required scope", "request_id": "7f3a9c2e" }}Secrets subsystem isn’t configured on this CP (secrets_disabled).
object
object
Closed-enum slug (e.g. permission_denied, validation_error, workspace_not_found)
Human-readable summary
Server-generated request id for correlating logs
Optional structured context. Validation errors land at
details.fields as a per-field map.
object
Example
{ "error": { "code": "permission_denied", "message": "caller lacks required scope", "request_id": "7f3a9c2e" }}