Check a downloaded backup can start
Verifies that a one-off dump of the database can start: the dump tool is installed on the control plane and the database accepts the instance's admin login. Call it before `GET /v1/databases/{id}/dump` to report problems as an error instead of a failed download. Requires backup:write on the database.
Verifies that a one-off dump of the database can start: the dump tool is installed on the control plane and the database accepts the instance's admin login. Call it before GET /v1/databases/{id}/dump to report problems as an error instead of a failed download. Requires backup:write on the database.
Authorization
bearerAuth In: header
Path Parameters
uuidResponse Body
curl -X POST "https://example.com/v1/databases/497f6eca-6276-4993-bfeb-53cbbbba6f08/dump/check"Download a one-off backup GET
Streams a gzip-compressed SQL dump of the database (the same `pg_dump` / `mariadb-dump` output a stored backup contains) straight to the client as `<database>-<YYYYMMDD-HHMMSS>.sql.gz`. Nothing is stored: no backup destination is needed and no backup record is created. Errors before the first byte return JSON; a failure mid-stream truncates the file, which its gzip trailer check exposes. Requires backup:write on the database.
Import a SQL file POST
Applies a SQL dump (max 2 GB) to the database through the restore path, running as the database's read-write role — never as the instance admin. The staged file is deleted afterwards. Requires database:write and backup:write.