deploy.host-database.backupBack the database up now (kept 30 days)
The pool host takes it within seconds; it appears in get when done.
Request syntax
POST /deploy/api/apps/{id}/host-database/backupsPath parameters
idRequiredstring
Constraints: uuid
Response
202 with `data`: `requestId`, the backup request the pool host answers; a newer request replaces one not yet taken. 404 when the app has no active pool-host database, 400 for an app not on pooled hosting.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Fields of data
requestIdAlwaysstring
The request the pool host answers at its next pull
Checked against the handlers: every route test validates their answers against this schema.
Errors
- 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
- 401No credentials, or an access key that is unknown, revoked or expired.
- 403The caller's policies do not allow deploy:ManageHostDatabase on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
- 404The resource does not exist in your organization.
Examples
The required parameters only, with example values. Replace id and the other placeholders with your own.
dcloud deploy host-database backup idcurl -X POST "https://console.platform-development.deutschecloud.app/deploy/api/apps/id/host-database/backups" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY"Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_deploy_host-database_backup.