Full programmatic control,
zero UI required.
The Qovery REST API gives you complete access to every platform resource. Automate deployments, build custom dashboards, integrate with internal tools, or build your own CLI on top of Qovery.
What you get.
Complete REST API
Every action in the console and CLI is backed by a public API endpoint. Organizations, clusters, projects, environments, services, variables, secrets, deployments -- all covered.
Token-based authentication
Generate API tokens from the console. Scope them to organizations. Use them in scripts, pipelines, or server-to-server integrations.
Webhooks & events
Subscribe to deployment events via webhooks. Trigger Slack notifications, update internal dashboards, or chain workflows on deploy success or failure.
Environment export
Export any environment as Terraform manifests via a single API call. Migrate from click-ops to infrastructure as code in seconds.
Deployment history
Query the full deployment history of any service or environment. Filter by status, date range, or commit. Build audit trails for compliance.
What you can do.
Custom CI/CD pipelines
Call the Qovery API from any CI system to trigger deploys, wait for completion, and gate on health checks.
Internal developer portals
Build custom dashboards or integrate Qovery into your existing portal (Backstage, Port, Cortex) using the API.
ChatOps & automation
Wire the API into Slack bots, PagerDuty runbooks, or custom automation scripts. Deploy from a Slack command.
Make your first API call
- 01Generate an API token in the Qovery console
- 02Set the token as an environment variable
- 03Call any endpoint with curl or your HTTP library
- 04Explore the full API reference in the docs
$ export QOVERY_API_TOKEN="your-token" $ curl -s -H "Authorization: Token $QOVERY_API_TOKEN" \ https://api.qovery.com/organization | jq .
Build anything
on Qovery.
The API is the foundation. Everything else -- console, CLI, Terraform, MCP -- is built on top of it. So can you.