The Compose API lets you manage Docker Compose stacks as first-class services within Dokploy. Stacks can be sourced from Git repositories, deployed from built-in templates, or imported from existing Compose files. Each stack supports the same lifecycle operations as applications — deploy, redeploy, stop, start — plus Compose-specific features like service listing and isolated deployment modes.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 | /compose.create | Create a new Compose stack |
| GET | /compose.one | Fetch a single Compose stack by ID |
| POST | /compose.update | Update Compose stack configuration |
| POST | /compose.delete | Delete a Compose stack |
| POST | /compose.deploy | Deploy the Compose stack |
| POST | /compose.redeploy | Redeploy the Compose stack |
| POST | /compose.stop | Stop all services in the stack |
| POST | /compose.start | Start all services in the stack |
| GET | /compose.loadServices | List services defined in the Compose file |
| GET | /compose.templates | List available Compose templates |
| POST | /compose.deployTemplate | Deploy a stack from a template |
| GET | /compose.getConvertedCompose | Get the resolved Compose file content |
| POST | /compose.isolatedDeployment | Deploy a single service in isolation |
| POST | /compose.move | Move the stack to another environment |
| POST | /compose.refreshToken | Regenerate the webhook token |
| POST | /compose.cancelDeployment | Cancel a running or queued deployment |
| POST | /compose.import | Import a Compose stack from a file |
| GET | /compose.search | Search Compose stacks |
| POST | /compose.cleanQueues | Clear the deployment job queue |
| POST | /compose.clearDeployments | Remove old deployment records |
| POST | /compose.killBuild | Abort an in-progress build |
| POST | /compose.disconnectGitProvider | Remove the linked Git provider |
| GET | /compose.getDefaultCommand | Get the default deployment command |
Key Endpoints
POST /compose.create
Create a new Docker Compose stack in a project environment.
Display name of the Compose stack.
Target environment ID within a project.
Internal stack name used by Docker. Auto-generated if omitted.
Optional description.
Target server ID. Required in cloud mode.
Unique ID of the created Compose stack.
Internal Docker stack name.
Initial status:
idle, running, done, or error.POST /compose.deploy
Trigger a full deployment of the Compose stack, pulling images and applying the Compose file.
ID of the Compose stack to deploy.
Optional label shown in deployment history.
Optional deployment notes.
POST /compose.deployTemplate
Create and deploy a new Compose stack directly from a built-in template. This is the fastest way to spin up popular stacks like WordPress, Nextcloud, or Plausible.
Template identifier (use
/compose.templates to list available IDs).Target environment ID.
Target server ID. Required in cloud mode.
GET /compose.loadServices
List all service names defined in the stack’s Compose file. Useful for populating domain or monitoring configuration.
ID of the Compose stack.
Compose mode —
docker-compose (default) or stack.POST /compose.redeploy
Re-run the last deployment of the Compose stack without re-cloning the source.
ID of the Compose stack.
Optional label for the redeployment entry.
Notes
Use
/compose.templates to browse all built-in templates before deploying with deployTemplate. Templates are fetched from the Dokploy GitHub repository and may vary by version.