Skip to main content
DELETE
Delete database
Queues guarded database deletion. The request must confirm the exact internal database name. DBHost creates and verifies a deletion backup, removes routing, and creates a tombstone with a seven-day self-service recovery window. The tombstone does not consume active database quota but reserves the name.
Deletion requires an authenticated API key with access to the database, the exact managed-registry/OID identity, a verified backup and a bound operation ID. Unsafe, unmanaged and protected targets receive FEATURE_NOT_AVAILABLE; a name alone is never authority.

Path parameters

Request

The operation validates ownership, database ID/name binding, managed-registry membership, destructive capability, and the permanent protected-target list. Names alone are never sufficient authorization.

Response

202 Accepted
Poll GET /api/v1/operations/{id}. After success, use the deleted-databases endpoint to inspect the recovery deadline or queue recovery while quota permits.

Errors