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 Account API

The Account API from Monitive — 16 operation(s) for account.

Monitive Account 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 Account. The published artifact set on APIs.io includes an OpenAPI specification and 6 JSON Schemas.

This API exposes 19 operations across 16 paths, and defines 11 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.

19 operations 16 paths 11 schemas 1 DELETE8 GET2 PATCH8 POST

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 Account 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 19

Across 16 paths, the API surfaces 19 operations — 1 DELETE, 8 GET, 2 PATCH, 8 POST. Each is listed below with its method, path, parameters, and response codes.

Account 19
GET
/api/v1/me
Get the signed-in user's identities
getMe → 200401
POST
/api/v1/me/account
Switch the signed-in session's current account
switchAccount body → 200400401403422
GET
/api/v1/me/reports
Get the signed-in user's weekly/monthly report preferences (issue
getReportPrefs → 200403
PATCH
/api/v1/me/reports
Update the signed-in user's weekly/monthly report preferences (issue
setReportPrefs body → 200400403
POST
/api/v1/me/identities/github
Start linking a GitHub identity onto the signed-in user
startGitHubLink → 201403
GET
/api/v1/me/invites
List invites addressed to the signed-in user's GitHub identity
listMyInvites → 200403
POST
/api/v1/me/invites/{inviteID}/accept
Accept an invite
acceptInvite 1 param → 200403404409
POST
/api/v1/account/invites
Invite a GitHub user to the account
createInvite body → 201400404409502
GET
/api/v1/account/invites
List live invites on the account
listInvites → 200403
DELETE
/api/v1/account/invites/{inviteID}
Revoke an invite
revokeInvite 1 param → 204404
POST
/api/v1/me/identities/google
Start linking a Google identity onto the signed-in user
startGoogleLink → 201403404503
POST
/api/v1/me/identities/email/start
Start linking an email identity onto the signed-in user
startEmailLink body → 202400403413415503
POST
/api/v1/me/identities/email/verify
Verify and complete an email identity link
verifyEmailLink body → 200401403409415503
GET
/api/v1/account
Get the authenticated account
getAccount → 200401403429
PATCH
/api/v1/account
Update the authenticated account's notificationemail
patchAccount body → 200400401403413415429
GET
/api/v1/account/usage
Get daily usage rows for the authenticated account
getAccountUsage 1 param → 200400401403429
GET
/api/v1/account/events
List the authenticated account's audit events
listAccountEvents 7 params → 200400401403429
GET
/api/v1/account/feed-token
Get the current feed token for the authenticated account
getApiV1AccountFeedToken → 200401403429
POST
/api/v1/account/feed-token/rotate
Rotate the feed token (old token stops working immediately)
postApiV1AccountFeedTokenRotate → 200401403429

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are Account (12 properties), AccountUsage (11 properties), AccountEvent (8 properties), UserInvite (6 properties). Each schema is shown below with its type and property counts.

AccountEventList
object
2 properties
UserInvite
object
An invite addressed to the signed-in user, as seen via GET /api/v1/me/invites (issue
6 properties
AccountUsage
object
Nine daily usage counters keyed on (accountid, date), written by usage.Worker (internal/usage). The source-derived totals behind all nine columns stop changing…
11 properties
AccountPatchInput
object
1 property 1 required
ReportPreferences
object
A signed-in user's weekly/monthly uptime-report opt-ins on one account (issue 357) — stored per accountmembers row, not per user, so leaving one team's reports…
5 properties
Account
object
12 properties
Invite
object
An owner-issued invitation, as seen by the account's owners (issue
6 properties
AccountEvent
object
One row of the per-account audit log. Mirrors the accountevents table verbatim (see SPEC §Account Events). payload is the recorder's bytes round-tripped withou…
8 properties
FeedTokenResponse
object
1 property
Error
object
1 property 1 required
AccountUsageResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Monitive publishes across the network.

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 Monitors API
Monitive OAuth API
Monitive Public API
Monitive Push API
Where this information came from

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