Skip to main content

Introduction

Welcome to the Qovery API Reference! The Qovery API is a REST API that allows you to programmatically manage your entire infrastructure.

Authentication

All API requests require authentication using an API token. Include your API token in the Authorization header of every request:
Token vs Bearer: Qovery API supports two authentication schemes:
  • Token (Recommended): Use for API tokens generated from Qovery Console. Format: Authorization: Token <your-api-token>
  • Bearer: Use for JWT tokens only (e.g., from OAuth flows). Format: Authorization: Bearer <jwt-token>
For third-party API integrations and programmatic access, always use Token authentication with API tokens. JWT tokens with Bearer are intended for internal use cases only and are not recommended for external API calls.

Creating an API Token

  1. Log in to the Qovery Console
  2. Navigate to Organization SettingsAPI Tokens
  3. Click Generate Token
  4. Give your token a descriptive name and set appropriate permissions
  5. Copy and save the token securely (it will only be displayed once)

Example Request

Replace YOUR_API_TOKEN with your actual API token generated from Qovery Console.

Token Security

API tokens provide access to your infrastructure. Keep them secure:
  • Never commit tokens to version control
  • Store them in environment variables or secrets management systems
  • Rotate tokens regularly
  • Use minimal required permissions

Official SDKs

Qovery provides official client libraries to simplify API integration:

TypeScript/JavaScript

Install via npm:
Usage:
Resources:

Go

Install via go get:
Usage:
Resources:

Other Languages

For other languages, you can:
  1. Use the REST API directly - All endpoints are documented in this reference
  2. Generate a client - Use the OpenAPI specification with code generation tools like:

Base URL

All API requests should be made to:

API Versioning

The current API version is included in the URL path:
We maintain backward compatibility within a major version. Breaking changes will result in a new major version (v2, v3, etc.).

Rate Limits

  • 1000 requests per hour per API token
  • Rate limit headers are included in all responses:
    • X-RateLimit-Limit: Maximum requests per window
    • X-RateLimit-Remaining: Remaining requests
    • X-RateLimit-Reset: Time when limit resets (Unix timestamp)
If you exceed the rate limit, you’ll receive a 429 Too Many Requests response.

Response Format

All successful responses return JSON:

Error Handling

Error responses include a status code and error details:

Common Status Codes

Pagination

List endpoints support pagination:
Response includes pagination metadata:

Try It Out

Use the interactive API reference on the right to explore endpoints and make test requests. Each endpoint includes:
  • Request parameters - Path, query, and body parameters
  • Example requests - Code samples in multiple languages
  • Responses - Expected response formats
  • Try it out - Test the API directly from the documentation

Next Steps

Explore Endpoints

Browse all available API endpoints in the reference

Code Examples

See practical examples and common workflows

TypeScript SDK

Use the official TypeScript client

Go SDK

Use the official Go client

Support

Need help with the API?