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

VividCortex Alerts API

Alert configuration, destinations, and integrations.

VividCortex Alerts API is one of 5 APIs that VividCortex publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Alerts. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 10 operations across 7 paths, and defines 1 schema. It is described by OpenAPI 3.1.0, at version 2.0.

Requests are made against a single base URL, https://app.vividcortex.com/api/v2.

10 operations 7 paths 1 schemas 1 DELETE6 GET1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2.0
Base URL
https://app.vividcortex.com/api/v2
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

VividCortex Alerts API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Per-environment API token created in DPM Settings → API Tokens and passed as Authorization: Bearer . Tokens are role-scoped (RBAC).

Paths & Operations 10

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

Alerts 10

Alert configuration, destinations, and integrations.

GET
/config/alerts
List alerts
listAlerts → 200401
POST
/config/alerts
Create an alert
createAlert body → 200400401
PUT
/config/alerts/{id}
Update an alert
updateAlert 1 param body → 200401404
DELETE
/config/alerts/{id}
Delete an alert
deleteAlert 1 param → 204401404
GET
/config/alerts/{id}/config
Get alert configuration
getAlertConfig 1 param → 200401404
PUT
/config/alerts/{id}/config
Update alert configuration
updateAlertConfig 1 param body → 200401404
GET
/config/integrations
List alert integrations
listIntegrations → 200401
GET
/config/destinations
List alert destinations
listDestinations → 200401
GET
/config/alert-opts/policy
List alert policies
listAlertPolicies → 200401
GET
/config/alert-opts/durations
List alert durations
listAlertDurations → 200401

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is Alert (6 properties). Each schema is shown below with its type and property counts.

Alert
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vividcortex-alerts-api-openapi.yml Raw ↑

Other APIs VividCortex publishes across the network.

VividCortex Events API
VividCortex Hosts API
VividCortex Metrics API
VividCortex Queries API
Where this information came from

This is an independent, third-party profile of VividCortex Alerts 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.