Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Hyperping Monitors API

Create, retrieve, update, and delete uptime monitors.

Hyperping Monitors API is one of 7 APIs that Hyperping 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 5 operations across 2 paths, and defines 2 schemas. It is described by OpenAPI 3.0.1, at version 1.0.

Requests are made against a single base URL, https://api.hyperping.io/v1.

5 operations 2 paths 2 schemas 1 DELETE2 GET1 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.hyperping.io/v1
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

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

  • bearerAuth — Project API key issued from the Developers tab in project settings, sent as Authorization: Bearer $USERAPIKEY. Keys can be Read & Write or Read-only. A missing…

Paths & Operations 5

Across 2 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.

Monitors 5

Create, retrieve, update, and delete uptime monitors.

GET
/monitors
List all monitors
listMonitors → 200
POST
/monitors
Create a new monitor
createMonitor body → 201
GET
/monitors/{monitor_uuid}
Retrieve a monitor
getMonitor 1 param → 200
PUT
/monitors/{monitor_uuid}
Update a monitor
updateMonitor 1 param body → 200
DELETE
/monitors/{monitor_uuid}
Delete a monitor
deleteMonitor 1 param → 204

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Monitor (11 properties), MonitorInput (8 properties). Each schema is shown below with its type and property counts.

Monitor
object
11 properties
MonitorInput
object
8 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hyperping-monitors-api-openapi.yml Raw ↑

Other APIs Hyperping publishes across the network.

Hyperping Healthchecks API
Hyperping Incidents API
Hyperping Maintenance API
Hyperping Outages API
Hyperping Reports API
Hyperping Status Pages API