How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Qovery Terraforms API

The Terraforms API from Qovery — 3 operation(s) for terraforms.

Qovery Terraforms API is one of 94 APIs that Qovery publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Terraforms. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, an API reference, authentication docs, and rate-limit docs.

This API exposes 4 operations across 3 paths, and defines 25 schemas. It is described by OpenAPI 3.2.0, at version 1.0.4.

Requests are made against a single base URL, https://api.qovery.com.

4 operations 3 paths 25 schemas 2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.4
Base URL
https://api.qovery.com
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

Qovery Terraforms API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). An API key is passed in the header as Authorization (ApiKeyAuth). By default, every request must be authenticated.

  • bearerAuth — JWT tokens should be used with OIDC account (human to machine). JWT tokens used by the Qovery console to communicate with the API have a TTL. Curl Example ' cu…
  • ApiKeyAuth — Token API are generated by Qovery to manage machine to machine interaction and do not have a TTL. Curl Example ' curl https://console.qovery.com/organization -…

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 2 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Terraforms 4
GET
/environment/{environmentId}/terraform
List terraforms
listTerraforms 1 param → 200401403404
POST
/environment/{environmentId}/terraform
Create a terraform
createTerraform 1 param body → 201400401403404409
GET
/defaultTerraformAdvancedSettings
List default terraform advanced settings
getDefaultTerraformAdvancedSettings → 200401403
POST
/terraform/{terraformId}/clone
Clone terraform
cloneTerraform 1 param body → 202401403404409

Schemas 25

The contract defines 25 schemas that model the data the API accepts and returns. The most detailed are TerraformRequest (14 properties), ApplicationGitRepository (13 properties), TerraformAdvancedSettings (8 properties), TerraformGitRepositoryRequest (4 properties). Each schema is shown below with its type and property counts.

TerraformVariablesSourceRequest
object
2 properties 2 required
ReferenceObject
object
1 property 1 required
TerraformRequest
object
14 properties 9 required
TerraformAutoDeployConfig
object
2 properties 2 required
ServiceTypeEnum
string
type of the service (application, database, job, ...)
ApplicationGitRepository
object
13 properties 4 required
TerraformJobResourcesResponse
object
4 properties 4 required
TerraformGitRepositoryRequest
object
4 properties 1 required
Base
object
3 properties 2 required
TerraformProviderVersion
object
2 properties 1 required
TerraformBackendUserProvided
object
User-provided backend configuration
TerraformEngineEnum
TerraformBackendKubernetes
object
Kubernetes-specific backend configuration
TerraformVariablesSourceResponse
object
2 properties 2 required
TerraformRequestJobResources
object
4 properties 4 required
TerraformResponseList
object
1 property
GitProviderEnum
string
TerraformBackend
Configuration for Terraform backend - exactly one backend type must be specified
TerraformFilesSource
object
1 property
DockerfileFragmentInline
object
Define Dockerfile commands directly in the configuration.
2 properties 2 required
TerraformVarKeyValue
object
A Terraform input variable
3 properties
CloneServiceRequest
object
2 properties 2 required
TerraformAdvancedSettings
object
8 properties
DockerfileFragmentFile
object
Reference a Dockerfile fragment file from your Git repository.
2 properties 2 required
TerraformResponse
A Terraform service

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

qovery-terraforms-api-openapi.yml Raw ↑

Other APIs Qovery publishes across the network.

Qovery Account Info API
Qovery Alert Receivers API
Qovery Alert Rules API
Qovery Application Actions API
Qovery Application Configuration API
Qovery Application Custom Domain API
Qovery Application Deployment History API
Qovery Application Deployment Restriction API
Qovery Application Environment Variable API
Qovery Application Logs API
Qovery Application Main Calls API
Qovery Application Secret API
Where this information came from

This is an independent, third-party profile of Qovery Terraforms API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.