Databases
Delete Database
Permanently remove a database and all of its data.
DELETE
This action is irreversible. Deleting a database removes all of its associated data, including ingested content, memories, metadata schema, vector indices, and graphs. There is no soft-delete and no recovery window.
Query parameters
Deletion completion
Deletion is asynchronous. Treat deletion as complete when the database no longer appears inGET /databases, or when GET /databases/status?database=... returns DATABASE_NOT_FOUND.
After deletion completes, the same database can be used in a new POST /databases request. Until then, avoid recreating the database or retrying ingestion/query against it.
Behavior notes
- Stop in-flight work first: Stop all ingestion, polling, query, and background jobs targeting this database before deleting. Calls made after deregistration can fail with
DATABASE_NOT_FOUNDeven while infrastructure cleanup is still running. - Async cleanup: The endpoint returns immediately after deregistering the database. Infrastructure cleanup of vector stores, graphs, and storage objects runs in the background and may take a few minutes to complete.
- Repeat calls: Deleting an already-deleted database returns
404 DATABASE_NOT_FOUND. Deleting a database that is still provisioning or deleting is treated as a request to tear down that database.
Errors
Common codes:404 DATABASE_NOT_FOUND, 401 UNAUTHORIZED, 422 VALIDATION_ERROR. See Error Responses for the full list.
Authorizations
API key sent as a Bearer token: "Bearer prefix.secret"
Query Parameters
Database identifier to delete
Example:
"acme_corp"