Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Qovery Terraform Deployment History API

The Terraform Deployment History API from Qovery — 1 operation(s) for terraform deployment history.

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

Tagged areas include Terraform Deployment History. 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 1 operation across 1 path, and defines 16 schemas. It is described by OpenAPI 3.0.0, at version 1.0.4.

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

1 operations 1 paths 16 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 2

Qovery Terraform Deployment History 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 1

Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.

Terraform Deployment History 1
GET
/terraform/{terraformId}/deploymentHistoryV2
List terraform deployments
listTerraformDeploymentHistoryV2 2 params → 200401403404

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are DeploymentHistoryService (7 properties), Commit (7 properties), JobCronSchedule (4 properties), DeploymentHistoryAuditingData (4 properties). Each schema is shown below with its type and property counts.

JobCronSchedule
object
4 properties 3 required
DeploymentHistoryAuditingData
object
4 properties 3 required
PaginationData
object
2 properties 2 required
OrganizationEventOrigin
string
Origin of the organization event
ServiceTypeEnum
string
type of the service (application, database, job, ...)
ServiceSubActionEnum
string
JobLifecyleSchedule
object
2 properties 1 required
DeploymentHistoryService
object
7 properties 6 required
ServiceActionEnum
string
DeploymentHistoryServicePaginatedResponseListV2
StateEnum
string
DeploymentHistoryServiceDetails
object
Commit
object
7 properties 5 required
JobLifecycleTypeEnum
ServiceActionStatusEnum
string
StatusDetails
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

qovery-terraform-deployment-history-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