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 Alert Rules API

The Alert Rules API from Qovery — 3 operation(s) for alert rules.

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

Tagged areas include Alert Rules. 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 3 paths, and defines 20 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 3 paths 20 schemas 1 DELETE2 GET1 POST1 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 Alert Rules 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 3 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Alert Rules 5
POST
/alert-rules
Create alert rule
createAlertRule body → 201400401403
GET
/alert-rules/{alertRuleId}
Get alert rule
getAlertRule 1 param → 200401403404
PUT
/alert-rules/{alertRuleId}
Update alert rule
editAlertRule 1 param body → 200400401403404
DELETE
/alert-rules/{alertRuleId}
Delete alert rule
deleteAlertRule 1 param → 204401403404
GET
/organization/{organizationId}/alert-rules
List alert rules
getAlertRules 1 param → 200401403404

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are AlertRuleCreationRequest (12 properties), ServiceLightResponse (11 properties), AlertRuleEditRequest (9 properties), AlertRuleCondition (5 properties). Each schema is shown below with its type and property counts.

ServiceTypeEnum
string
type of the service (application, database, job, ...)
Base
object
3 properties 2 required
AlertRuleSource
Source of the alert rule: - MANAGED: Alert rule created and managed through the Qovery API - GHOST: Alert rule that exists in Prometheus but has been deleted f…
AlertPresentationResponse
object
2 properties
AlertRuleConditionKind
AlertRuleCreationRequest
object
12 properties 12 required
AlertRuleConditionOperator
ServiceLightResponse
object
11 properties 10 required
AlertTargetType
The target of an alert
AlertRuleResponse
AlertRuleResponseBase
object
Base schema for alert rule responses with discriminator
3 properties 3 required
AlertRuleState
AlertRuleList
object
1 property 1 required
AlertTarget
object
3 properties 2 required
AlertPresentation
object
2 properties
AlertRuleCondition
object
5 properties 2 required
AlertRuleEditRequest
object
9 properties 9 required
AlertRuleConditionFunction
AlertSeverity
Alert severity level: - LOW: Minor issues or informational alerts that don't require immediate attention. Can be addressed during normal business hours. - MEDI…
GhostAlertRuleResponse
Response for ghost alerts that exist in Prometheus but have been deleted from the database

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

qovery-alert-rules-api-openapi.yml Raw ↑

Other APIs Qovery publishes across the network.

Qovery Account Info API
Qovery Alert Receivers 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
Qovery Applications API
Where this information came from

This is an independent, third-party profile of Qovery Alert Rules 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.