The Backups API lets you create scheduled or on-demand backup jobs for all supported database types (PostgreSQL, MySQL, MariaDB, MongoDB) and Compose services. Backups are stored in a configured destination (S3-compatible bucket). Volume backups extend this to Docker named volumes, enabling point-in-time recovery of persistent data. You can also list stored backup files to audit retention.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/Nettalco/dokploy/llms.txt
Use this file to discover all available pages before exploring further.
Endpoints
| Method | Endpoint | Description |
|---|---|---|
| POST | /backup.create | Create a new backup schedule |
| GET | /backup.one | Fetch a backup schedule by ID |
| POST | /backup.update | Update a backup schedule |
| POST | /backup.remove | Delete a backup schedule |
| POST | /backup.manualBackupPostgres | Trigger an immediate PostgreSQL backup |
| POST | /backup.manualBackupMySql | Trigger an immediate MySQL backup |
| POST | /backup.manualBackupMariadb | Trigger an immediate MariaDB backup |
| POST | /backup.manualBackupCompose | Trigger an immediate Compose backup |
| POST | /backup.manualBackupMongo | Trigger an immediate MongoDB backup |
| POST | /backup.manualBackupWebServer | Trigger a web-server backup |
| GET | /backup.listBackupFiles | List stored backup files in a destination |
| GET | /volumeBackups.list | List volume backup schedules |
| POST | /volumeBackups.create | Create a volume backup schedule |
| GET | /volumeBackups.one | Fetch a volume backup by ID |
| POST | /volumeBackups.delete | Delete a volume backup schedule |
| POST | /volumeBackups.update | Update a volume backup schedule |
| POST | /volumeBackups.runManually | Trigger an immediate volume backup |
Key Endpoints
POST /backup.create
Create a scheduled backup for a database. Schedules use cron expressions.
Type of database:
postgres, mysql, mariadb, mongo.ID of the database to back up (field name must match
serviceType).ID of the backup destination (S3-compatible storage configured under Settings).
Cron expression for the backup schedule (e.g.,
0 2 * * * for daily at 2 AM).Object key prefix (folder path) inside the destination bucket.
Whether the schedule is active (default:
true).Unique ID of the created backup schedule.
POST /backup.manualBackupPostgres
Run an immediate PostgreSQL backup outside of the schedule.
ID of the backup schedule to execute immediately.
GET /backup.listBackupFiles
List all backup files stored in a destination bucket, optionally filtered by prefix.
ID of the backup schedule whose files to list.
Array of stored backup file objects.
Object key / filename in the destination bucket.
File size in bytes.
ISO timestamp of last modification.
POST /volumeBackups.create
Create a scheduled backup for a Docker named volume.
ID of the service that owns the volume.
Service type:
application, postgres, mysql, mariadb, mongo, redis, or compose.Name of the Docker named volume to back up.
ID of the backup destination.
Cron expression for the backup schedule.
Object key prefix inside the destination bucket.
Whether the schedule is active (default:
true).POST /volumeBackups.runManually
Immediately execute a volume backup outside the schedule.
ID of the volume backup schedule to run.
Notes
Backup destinations must be configured under Settings → Destinations before creating backup schedules. Destinations support S3-compatible storage (AWS S3, Cloudflare R2, MinIO, etc.).