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 Helm Main Calls API

The Helm Main Calls API from Qovery — 5 operation(s) for helm main calls.

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

Tagged areas include Helm Main Calls. 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 7 operations across 5 paths, and defines 38 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.

7 operations 5 paths 38 schemas 1 DELETE5 GET1 PUT

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 Helm Main Calls 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 7

Across 5 paths, the API surfaces 7 operations — 1 DELETE, 5 GET, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Helm Main Calls 7
GET
/helm/{helmId}
Get helm by ID
getHelm 1 param → 200401403404
PUT
/helm/{helmId}
Edit helm
editHelm 1 param body → 200400401403404409
DELETE
/helm/{helmId}
Delete helm
deleteHelm 1 param → 204401403404
GET
/helm/{helmId}/commit
List last helm commits
listHelmCommit 2 params → 200401403404
GET
/helm/{helmId}/status
Get helm status
getHelmStatus 1 param → 200401403404
GET
/helm/{helmId}/link
List all URLs of the helm
listHelmLinks 1 param → 200401403404
GET
/helm/{helmId}/listServices
Get helm kubernetes services
getHelmKubernetesServices 1 param → 200401403404

Schemas 38

The contract defines 38 schemas that model the data the API accepts and returns. The most detailed are ApplicationGitRepository (13 properties), Status (10 properties), HelmPortResponseBase (8 properties), Commit (7 properties). Each schema is shown below with its type and property counts.

ServiceActionEnum
string
HelmRequest
HelmSourceRepositoryResponse
object
3 properties 3 required
ServiceActionStatusEnum
string
StatusDetails
object
3 properties 3 required
Base
object
3 properties 2 required
HelmPortRequest
object
1 property
CommitResponseList
object
1 property
HelmPortResponseBase
object
8 properties 4 required
KubernetesService
object
2 properties 2 required
ApplicationGitRepository
object
13 properties 4 required
ServiceStepMetric
object
3 properties
HelmGitRepositoryRequest
object
4 properties 4 required
HelmPortResponseWithServiceSelectors
ServiceSubActionEnum
string
Commit
objectnull
7 properties 5 required
KubernetesSelector
object
2 properties 2 required
Status
object
10 properties 7 required
ServiceStepMetrics
object
3 properties 3 required
HelmPortResponseWithServiceName
HelmResponse
LinkResponseList
object
1 property
KubernetesServiceResponseList
object
1 property
HelmPortProtocolEnum
string
ApplicationGitRepositoryRequest
object
5 properties 4 required
ServiceTypeEnum
string
type of the service (application, database, job, ...)
KubernetesServicePort
object
2 properties 1 required
ServiceDeploymentStatusEnum
string
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.…
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…
HelmKeyValues
array
The input is in json array format: [ [$KEY,$VALUE], [...] ]
HelmSourceGitResponse
object
1 property 1 required
GitProviderEnum
string
StateEnum
string
Link
object
7 properties 7 required
ReferenceObject
object
1 property 1 required
KubernetesServiceSpec
object
3 properties
KubernetesMetadata
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

qovery-helm-main-calls-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 Helm Main Calls 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.