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

OpenStatus Monitor API

HTTP, TCP, and DNS uptime monitors.

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

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

This API exposes 7 operations across 4 paths, and defines 7 schemas. It is described by OpenAPI 3.0.1, at version 1.0.

Requests are made against a single base URL, https://api.openstatus.dev/v1.

7 operations 4 paths 7 schemas 1 DELETE3 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://api.openstatus.dev/v1
Authentication
API Key
License
Terms of Service
Resource Areas
1

Authentication & Security 1

OpenStatus Monitor API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-openstatus-key (apiKey). By default, every request must be authenticated.

  • apiKey — OpenStatus API key, created in the workspace settings.

Paths & Operations 7

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

Monitor 7

HTTP, TCP, and DNS uptime monitors.

GET
/monitor
List all monitors
getAllMonitors → 200401
POST
/monitor
Create a monitor
createMonitor body → 200400401
GET
/monitor/{id}
Get a monitor
getMonitor 1 param → 200401404
PUT
/monitor/{id}
Update a monitor
updateMonitor 1 param body → 200400401404
DELETE
/monitor/{id}
Delete a monitor
deleteMonitor 1 param → 200401404
GET
/monitor/{id}/summary
Get a monitor summary
getMonitorSummary 1 param → 200401404
POST
/monitor/{id}/run
Trigger a monitor run
runMonitor 1 param → 200401404

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are Monitor (18 properties), MonitorInput (15 properties), MonitorSummary (6 properties), CheckResult (5 properties). Each schema is shown below with its type and property counts.

CheckResult
object
5 properties
Assertion
object
A condition evaluated against the check response.
4 properties
MonitorSummary
object
6 properties
Monitor
object
18 properties
MonitorInput
object
15 properties 3 required
Error
object
2 properties
Header
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

openstatus-monitor-api-openapi.yml Raw ↑

Other APIs OpenStatus publishes across the network.

OpenStatus Check API
OpenStatus Incident API
OpenStatus Page API
OpenStatus Status Report API
Where this information came from

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