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 Applications API

The Applications API from Qovery — 4 operation(s) for applications.

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

Tagged areas include Application. 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 5 operations across 4 paths, and defines 55 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.

5 operations 4 paths 55 schemas 3 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 Applications 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 5

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

Applications 5
GET
/environment/{environmentId}/application
List applications
listApplication 2 params → 200401403404
POST
/environment/{environmentId}/application
Create an application
createApplication 1 param body → 201400401403404409
GET
/environment/{environmentId}/application/status
List all environment applications statuses
getEnvironmentApplicationStatus 1 param → 200401403404
GET
/defaultApplicationAdvancedSettings
List default application advanced settings
getDefaultApplicationAdvancedSettings → 200401403
POST
/application/{applicationId}/clone
Clone application
cloneApplication 1 param body → 202401403404409

Schemas 55

The contract defines 55 schemas that model the data the API accepts and returns. The most detailed are ApplicationAdvancedSettings (42 properties), ApplicationGitRepository (13 properties), Status (10 properties), ServicePort (9 properties). Each schema is shown below with its type and property counts.

BuildModeEnum
string
DOCKER requires dockerfilepath
ReferenceObject
object
1 property 1 required
ServiceLabelsRequestList
array
OrganizationAnnotationsGroupScopeEnum
string
Annotations Group Scope
ApplicationAdvancedSettings
object
42 properties
KedaAutoscalingResponse
ServiceTypeEnum
string
type of the service (application, database, job, ...)
ApplicationGitRepository
object
13 properties 4 required
OrganizationLabelsGroupResponseList
array
Healthcheck
object
2 properties
Base
object
3 properties 2 required
KedaTriggerAuthenticationRequest
object
2 properties 1 required
Probe
objectnull
6 properties
ServicePortRequest
object
1 property
Label
object
3 properties 3 required
KedaScalerResponse
ServicePortResponseList
array
ServiceStorage
object
1 property
ServiceActionEnum
string
ApplicationGitRepositoryRequest
object
5 properties 4 required
ServiceSubActionEnum
string
ServiceActionStatusEnum
string
OrganizationAnnotationsGroupResponseList
array
KedaScalerRole
string
StorageTypeEnum
string
OrganizationLabelsGroupResponse
StatusDetails
object
3 properties 3 required
ServiceStepMetrics
object
3 properties 3 required
ServiceStepMetricNameEnum
string
The name of the deployment step at the service level: - REGISTRYCREATEREPOSITORY: The step to create the repository in the registry. - GITCLONE: The step to cl…
ApplicationRequest
KedaScalerRequest
object
6 properties 2 required
ServiceStorageRequest
object
1 property
ServiceLabelRequest
object
1 property 1 required
KedaAutoscalingRequest
object
4 properties 2 required
StepMetricStatusEnum
string
The status of completion for the step: - SUCCESS: The step completed successfully. - ERROR: The step completed with an error. - CANCEL: The step was canceled.…
GitProviderEnum
string
AutoscalingMode
string
ReferenceObjectStatus
Application
Annotation
object
2 properties 2 required
ServiceDeploymentStatusEnum
string
ServiceStepMetric
object
3 properties
KedaTriggerAuthenticationResponse
AutoscalingPolicyRequest
ServiceAnnotationRequest
object
1 property 1 required
Status
object
10 properties 7 required
StateEnum
string
PortProtocolEnum
string
AutoscalingPolicyResponse
CloneServiceRequest
object
2 properties 2 required
ServicePort
object
9 properties 4 required
OrganizationAnnotationsGroupResponse
ReferenceObjectStatusResponseList
object
1 property
ServiceAnnotationsRequestList
array
ApplicationResponseList
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

qovery-applications-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 Applications 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.