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

Monitive Monitors API

The Monitors API from Monitive — 7 operation(s) for monitors.

Monitive Monitors API is one of 15 APIs that Monitive publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 6 JSON Schema definitions.

Tagged areas include Monitors. The published artifact set on APIs.io includes an OpenAPI specification and 6 JSON Schemas.

This API exposes 14 operations across 7 paths, and defines 18 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against a single base URL, https://api.uptimemonitoring.com.

14 operations 7 paths 18 schemas 2 DELETE6 GET2 POST4 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.uptimemonitoring.com
Authentication
HTTP Bearer
License
Proprietary
Resource Areas
1

Authentication & Security 1

Monitive Monitors API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth).

  • bearerAuth — API key (umklive) or session token from OAuth exchange.

Paths & Operations 14

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

Monitors 14
GET
/api/v1/monitors
List monitors
listMonitors → 200401403405429
POST
/api/v1/monitors
Create monitor
createMonitor body → 201400401403409413415429
GET
/api/v1/monitors/{monitorID}
Get monitor
getMonitor 1 param → 200400401403404429
PUT
/api/v1/monitors/{monitorID}
Update monitor
updateMonitor 1 param body → 200400401403404409413415
DELETE
/api/v1/monitors/{monitorID}
Delete monitor
deleteMonitor 1 param → 204400401403404429
GET
/api/v1/monitors/{monitorID}/webhookdeprecated
Deprecated: get the legacy single webhook configured for a monitor
getMonitorWebhook 1 param → 200404429
PUT
/api/v1/monitors/{monitorID}/webhookdeprecated
Deprecated: create or replace the legacy single webhook for a monitor
putMonitorWebhook 1 param body → 200400404413415429
DELETE
/api/v1/monitors/{monitorID}/webhookdeprecated
Deprecated: remove the legacy single webhook from a monitor
deleteMonitorWebhook 1 param → 204404429
GET
/api/v1/monitors/{monitorID}/recipients
List recipient ids attached to a monitor
getMonitorRecipients 1 param → 200404429
PUT
/api/v1/monitors/{monitorID}/recipients
Replace the set of recipients attached to a monitor
putMonitorRecipients 1 param body → 200400404413415429
GET
/api/v1/monitors/{monitorID}/uptime
Per-day uptime grid for a monitor
getMonitorUptime 2 params → 200400401403404429
GET
/api/v1/monitors/{monitorID}/status-page
Get the monitor's free status-page switch state (issue
getMonitorStatusPage 1 param → 200401403404
PUT
/api/v1/monitors/{monitorID}/status-page
Turn the monitor's free status page on or off (issue
setMonitorStatusPage 1 param body → 200400401403404413415
POST
/api/v1/monitors/{monitorID}/test
Dispatch an ad-hoc check from the probe fleet
testMonitor 2 params → 200400403404429502503

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are Monitor (19 properties), CheckResult (12 properties), MonitorInput (12 properties), TestResult (10 properties). Each schema is shown below with its type and property counts.

MonitorInput
object
All string fields must be valid UTF-8 with no null bytes. URL fields must additionally be free of ASCII control characters (U+0000..U+001F and U+007F). Violati…
12 properties
MonitorListItem
Monitor with inline status summary for list views.
StatusPageSettings
object
The owner's free status-page switch state for one monitor (issue 368). url is null when the page is off.
2 properties 2 required
MonitorRecipients
object
GET/PUT responses always carry both recipientids and recipients (resolved from the same snapshot), so a client reading either field sees the attached set. PUT…
2 properties
UptimeDay
object
One day's uptime entry returned by GET /api/v1/monitors/{monitorID}/uptime. pct is nullable: null means the day had no scheduled checks (render grey). A numeri…
4 properties 4 required
MonitorCreateInput
POST /api/v1/monitors's own request shape (issue 329): MonitorInput plus recipientids/recipients. Not used by PUT /monitors/{id}, which stays on plain MonitorI…
SoftCapNotice
object
Advisory attached to POST /api/v1/monitors when the post-insert per-account monitor count falls in the soft-cap window (51..100). Clients should branch on code…
5 properties 5 required
MonitorState
object
9 properties
RequestHeader
object
One custom request header (issue 364). Write-only: the value itself is never present on a read — only whether one is set.
2 properties 2 required
Monitor
object
19 properties
Timings
object
6 properties
MaintenanceWindow
object
A monitor's single alert-silencing window (issue 361). Always present on a Monitor; {"type":"none"} (the default) silences nothing. Accepted on MonitorInput/Mo…
6 properties
TestResult
object
10 properties
Webhook
object
Configured notification endpoint. The signed JSON body for an HTTP attempt contains event, monitorref, accounthandle (issue 412 — replaced the old numeric moni…
5 properties
CheckResult
object
12 properties
Error
object
1 property 1 required
MonitorDetail
object
5 properties
HostFanError
object
429 body returned when the host-fan heuristic trips on POST /api/v1/monitors, or on a PUT /api/v1/monitors/{monitorID} that changes url or type (issue 335). Th…
4 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

uptimemonitoring-com-monitors-api-openapi.yml Raw ↑

Other APIs Monitive publishes across the network.

Monitive Account API
Monitive Admin API
Monitive Announcements API
Monitive Email API
Monitive Events API
Monitive Feed API
Monitive Feed.xml API
Monitive Incidents API
Monitive Keys API
Monitive OAuth API
Monitive Public API
Monitive Push API
Where this information came from

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