Delete a vault
⚠️
Preview — this feature is being built; the design below is the spec.
DELETE https://app.syntic.ai/v1/vaults/{vault_id}Delete a vault and every secret in it. Refused while an agent or environment references the vault.
For how this fits into a full workflow, see Credential vaults.
Headers
| Header | Required | Value |
|---|---|---|
Authorization | Yes | Bearer <key>: a private inference key (sk_live_...). See Authentication. |
syntic-beta | Yes, while in preview | agents-2026-11-01. Without it the call fails with 400 beta_required. See Versioning. |
Path parameters
| Parameter | Type | Description |
|---|---|---|
vault_id | string | The vault id, starting with vlt_. |
Response
200 OK, Content-Type: application/json
{
"id": "vlt_01JC2B4D6F8H0K2M4P6R",
"type": "vault_deleted"
}Examples
curl -sS -X DELETE https://app.syntic.ai/v1/vaults/vlt_01JC2B4D6F8H0K2M4P6R \
-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:
| Status | type | code | When |
|---|---|---|---|
| 400 | invalid_request_error | beta_required | The syntic-beta header is missing. |
| 403 | permission_error | role_required | The key’s creator is not an Administrator or Owner. |
| 404 | not_found_error | vault_not_found | No vault with that id in this workspace. |
| 409 | conflict_error | vault_in_use | An agent or environment references it. |
| 401 | authentication_error | invalid_api_key | The key is missing, unknown, revoked or expired. |
| 429 | rate_limit_error | rate_limited | Too 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?