Core Concepts
Application Lifecycle
Applications in Dokploy follow a complete lifecycle:- Create: Initialize a new application with basic configuration
- Configure: Set up source providers, build settings, and environment variables
- Deploy: Build and deploy your application
- Manage: Start, stop, reload, and monitor running applications
- Update: Modify configuration and redeploy
- Delete: Remove applications and clean up resources
Application Status
Applications can be in one of four states:idle- Application is not runningrunning- Application is currently building or deployingdone- Application is successfully deployed and runningerror- Application encountered an error during deployment
Source Types
Dokploy supports multiple source types for deploying applications:- github - Deploy from GitHub repositories
- gitlab - Deploy from GitLab repositories
- bitbucket - Deploy from Bitbucket repositories
- gitea - Deploy from Gitea repositories
- docker - Deploy from Docker images in registries
- git - Deploy from custom Git repositories with SSH keys
- drop - Deploy by uploading a ZIP file
Build Types
Applications can be built using different build strategies:- nixpacks (default) - Automatic buildpack detection
- dockerfile - Use Dockerfile for building
- heroku_buildpacks - Heroku buildpacks support
- paketo_buildpacks - Cloud Native Buildpacks
- railpack - Specialized Rails buildpack
- static - Static site deployment
Available Endpoints
Application Management
Create Application
Create a new application with basic configuration
Get Application
Retrieve detailed information about an application
Update Application
Update application settings and configuration
Delete Application
Remove an application and clean up resources
Deployment Operations
Deploy Application
Trigger a new deployment from source
Redeploy Application
Rebuild and redeploy the current version
Cancel Deployment
Cancel an in-progress deployment
Application Control
Start Application
Start a stopped application container
Stop Application
Stop a running application container
Reload Application
Reload application configuration without redeploying
Authentication
All Application API endpoints require authentication using a Bearer token in the Authorization header:Base URL
All API requests should be made to:Common Parameters
Application ID
Most endpoints require anapplicationId parameter to identify the specific application:
Environment ID
When creating applications, you must specify anenvironmentId to associate the application with a project environment:
Response Format
API responses return JSON objects with relevant data. Error responses follow this format:Rate Limiting
API requests are subject to rate limiting based on your Dokploy instance configuration. Check the response headers for rate limit information.Next Steps
Create Your First Application
Learn how to create applications via the API
Deploy Applications
Trigger deployments and manage the deployment lifecycle