domain: docs.dokploy.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
As an admin, go to /settings/profile → API/CLI section to generate an access token (JWT-based)
If deploying as a non-admin user, have an administrator grant Swagger UI / token access first — users have none by default
Call POST http://<dokploy-host>:3000/api/application.create with header x-api-key: <token>
Explore the full endpoint set interactively at http://<dokploy-host>:3000/swagger
Use companion endpoints (e.g. under the Application/Compose/Domain reference groups) to set source, build type, and domains after creation
Known gotchas
Auth uses the x-api-key header, not an Authorization: Bearer header like several competing PaaS APIs
The base OpenAPI path is /api (no /v1 version prefix), unlike Coolify's /api/v1
Swagger UI access is restricted to authenticated administrators by default — a 401/403 there means the account lacks API access, not that the server is misconfigured
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?