Hyperping Incidents API
Status page incident lifecycle and updates.
Hyperping Incidents API is one of 7 APIs that Hyperping publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Incidents. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 6 operations across 3 paths, and defines 3 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.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Hyperping Incidents 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 6
Across 3 paths, the API surfaces 6 operations — 1 DELETE, 2 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Status page incident lifecycle and updates.
Schemas 3
The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Incident (8 properties), IncidentInput (5 properties), IncidentUpdate (3 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Hyperping 6
Other APIs Hyperping publishes across the network.