Skip to Content
DocumentationAPI ReferenceOverview

API Reference

The Launcher API is a RESTful HTTP API that provides programmatic access to all platform resources.

Base URL

https://plane.lnchr.cloud/<tenant-id>/api/v1

Authentication

All endpoints require authentication unless otherwise noted. Two methods are supported:

MethodHeaderUse Case
Bearer TokenAuthorization: Bearer <jwt>Dashboard, interactive sessions
Service Keyx-lnchr-key: <key>CI/CD, Terraform, automation, AI agents

Service keys are recommended for programmatic access. Create one via Settings > Service Keys in the dashboard or the Authentication API.

Response Format

All responses use a standard JSON envelope:

// Success (200, 201) { "success": true, "data": { ... } } // Error (4xx, 5xx) { "success": false, "error": { "code": "NOT_FOUND", "message": "application not found" } } // No Content (204) — empty body

Error Codes

HTTP StatusCodeDescription
400BAD_REQUESTInvalid request body or parameters
401UNAUTHORIZEDMissing or invalid authentication
403FORBIDDENInsufficient permissions
404NOT_FOUNDResource does not exist
409CONFLICTResource already exists or state conflict
429TOO_MANY_REQUESTSRate limit exceeded
500INTERNAL_ERRORUnexpected server error
503SERVICE_UNAVAILABLEServer temporarily unavailable

Conventions

  • All resource IDs are UUIDs (e.g., 550e8400-e29b-41d4-a716-446655440000)
  • All timestamps are RFC 3339 UTC (e.g., 2024-01-15T10:30:00Z)
  • List endpoints support ?projectId= to filter by project
  • Every response includes the x-plane-version header with the server version

Quick Example

# Create a service key curl -X POST https://plane.lnchr.cloud/<tenant>/api/v1/settings/service-keys \ -H "Authorization: Bearer <jwt>" \ -H "Content-Type: application/json" \ -d '{"name": "ci-cd"}' # Use the service key to list applications curl https://plane.lnchr.cloud/<tenant>/api/v1/applications \ -H "x-lnchr-key: <service-key>" # Deploy an application curl -X POST https://plane.lnchr.cloud/<tenant>/api/v1/applications/<id>/deploy \ -H "x-lnchr-key: <service-key>"

Sections

SectionDescription
AuthenticationLogin, registration, service keys, user profile
ProjectsProjects, members, invites, environments
ServersServer management, status, diagnostics
ApplicationsApp lifecycle, deploy, scale, env vars
DatabasesManaged databases (Postgres, MySQL, Redis, MongoDB)
BucketsS3-compatible object storage (MinIO)
FunctionsServerless functions with HTTP/cron triggers
VolumesPersistent storage volumes
Environment VariablesEncrypted env vars with reference resolution
DomainsCustom domain management and DNS verification
DeploymentsDeployment history and logs
BackupsBackup destinations, schedules, PITR
TemplatesInfrastructure-as-code templates
RegistriesContainer registry credentials
Git ProvidersGitHub, GitLab, Bitbucket integrations
MonitoringServer metrics and application traffic
IssuesError tracking and issue management
AlertsAlert channels (Slack, Discord, email, webhooks)
NotificationsIn-app notification management
SearchGlobal resource search
WebhooksGit webhook endpoints for auto-deploy
WebSocket EndpointsReal-time logs, metrics, terminal
MCP IntegrationAI agent integration via Model Context Protocol
Last updated on