LaunchDeploy

Account

API & CLI

Everything, from the terminal

Every action in the web app is available as JSON under /api/v1: connect providers, list repositories and domains, create a project, start a launch and poll its tasks, manage nameservers, DNS, email, deployments, environment variables, health checks and fixes. The LaunchDeploy CLI and MCP server are built on this API.

Tokens

Create a personal access token under Account → Security → API tokens. A token acts as you inside the workspace that was current when you created it; it cannot reach other workspaces. Tokens start with ld_, are shown once, can expire, and can be revoked at any time. Send it as a Bearer header: Authorization: Bearer ld_...

Launch flow

GET /api/v1/providers to see what to connect and which credential fields each needs. Address a provider by key: POST /api/v1/integrations/github with credentials, GET /api/v1/integrations/github for status, GET /api/v1/integrations/github/repositories to pick a repo. GET /api/v1/projects/{project}/integrations shows that project's stack. POST /api/v1/projects with the same fields as the launch wizard; the response includes the planned launch. POST /api/v1/projects/{project}/launches/{launch}/start, then GET the launch until status is complete. Business-rule refusals (missing provider, launch already running) return 409 with a human message; validation returns 422.

Secrets

Environment variable values are never returned by list endpoints. POST /api/v1/projects/{project}/environment/values with your account password to fetch them from the host, rate-limited like the web app.