HostTracker

Append an update to a declared incident's timeline (and move its state, e.g. to 'resolved'). Scope 'statuspage:write'. This too is PUBLISHED and notifies subscribers — get the wording approved first.

Call any HostTracker v2 REST operation that no curated tool covers. Look the operation up with describe_api first — the method and path must match a real operation or the call is refused. The caller's token supplies authorisation and its scopes still apply. Writes under /account are refused outright by this server's safety policy. A DELETE, and any bulk write that is not a /validate dry-run, is refused unless confirmed=true - confirm with the user first, then retry with confirmed=true.

Create many monitors in one asynchronous job. Scope 'monitor:write'. The batch is validated first and, unless submit is true, only the validation report comes back — show it to the user, then call again with submit=true. The submitted job is polled with get_job.

Delete every monitor a filter selects, as an asynchronous job. HIGHLY DESTRUCTIVE — always show the user the validation count first and get an explicit go-ahead. Called without expectedCount it only validates; the submission needs BOTH confirmed=true and the expectedCount the validation reported, and the API refuses it if the selection drifted meanwhile. Scope 'monitor:write'.

Apply one patch to every monitor a filter selects, as an asynchronous job. Scope 'monitor:write'. Without submit=true only the count and a sample of what would be touched come back — show that to the user first.

Cancel a queued or running asynchronous operation. Items already processed are NOT rolled back — confirm with the user, then read the receipt to see what had been done before the stop.

Annotate an incident with a note (for example the root cause) and get the incident back. Scope 'monitor:write'. The comment replaces any previous one.

Confirm a contact with the code it received. Scope 'contact:write'. Ask the user to read the code from their inbox or phone.

Copy a monitor to one or more new addresses, keeping its configuration. Scope 'monitor:write'. Copying many addresses answers with a job id — poll it with get_job.

Create a contact of type email, sms, voiceCall or webPush. Scope 'contact:write'. Sending to a person's address is a real-world action — confirm the address with the user first. The contact is created UNCONFIRMED: a confirmation code is sent to it, and confirm_contact must be called with that code before it receives alerts. For signed HTTP delivery use create_webhook instead.

Create a contact group: a named set of contacts, each with the events it should receive. Scope 'contact:write'.

Schedule a maintenance window over an explicit set of monitors. Scope 'monitor:write'. While it runs the covered monitors suppress alerts (and statistics, if asked). Times are Unix seconds.

Create a monitor. Scope 'monitor:write'. Confirm the target and interval with the user first — a monitor consumes an account slot and starts alerting. Attach contacts afterwards with subscribe_contact.

Create a status page. Scope 'statuspage:write'. The page becomes PUBLIC at its slug — agree the slug, the title and which monitors appear with the user before creating it.

Declare an incident or a scheduled maintenance on a status page. Scope 'statuspage:write'. This PUBLISHES the message to the page and notifies its subscribers — have the user approve the exact wording first.

Register a webhook. Scope 'webhook:write'. The url must be https and publicly reachable. Events are chosen from: monitor.down, monitor.up, monitor.repeatedlyDown, incident.opened, incident.closed, monitor.created, monitor.updated, monitor.deleted, maintenance.ended, certificate.expiring, domain.expiring, contact.confirmed, contact.updated. The response carries the signing secret once.

Delete a contact and every subscription it had. Scope 'contact:write'. DESTRUCTIVE — confirm with the user first (their monitors stop notifying that address), then report the receipt this returns.

Delete a contact group. Scope 'contact:write'. DESTRUCTIVE — confirm with the user first. The contacts themselves are not deleted.

Cancel a maintenance window. Scope 'monitor:write'. DESTRUCTIVE — confirm with the user first; cancelling an ACTIVE window makes its monitors start alerting again immediately.

Delete one monitor and its subscriptions. Scope 'monitor:write'. DESTRUCTIVE and not undoable — confirm with the user first, then report the deletion receipt this returns.

Delete a status page with its components, incidents and subscribers. Scope 'statuspage:write'. DESTRUCTIVE and public-facing — confirm with the user first; the slug stops resolving immediately.

Unregister a webhook and stop its deliveries. Scope 'webhook:write'. DESTRUCTIVE — confirm with the user first; pending deliveries are dropped and the signing secret cannot be recovered.

Describe the HostTracker v2 REST operations available through api_request: their paths, what each one does, its query parameters and its request-body members. Call it with a search term (e.g. 'contact', '/webhook', 'statuspage') before using api_request, so the call is built from the real contract rather than guessed. All timestamps in this API are Unix seconds and all ids are opaque strings.

Request an uptime report over a set of monitors and a time range. Scope 'monitor:read'. Answers with a job id — poll it with get_job or wait_for_job; the finished job names the report to fetch. Times are Unix seconds.

Read the account: identity, package, resource usage, limits and status flags. Scope 'account:read'. Read-only — this server cannot change account settings.

Read the API quota headroom and the scopes the current token actually carries. Scope 'account:read'. Call this first when another tool returns a 403 — it shows whether the token is simply missing a scope.

Read how many monitors, contacts, reports and maintenance windows the account uses out of what its package allows. Scope 'account:read'.

Fetch the current results of a previously started instant check by its dbId and id (as returned by run_instant_check). Requires a token with the 'check' scope.

Read one contact. Scope 'contact:read'. Add expand='subscription' to see what it is subscribed to.

Read one incident with the transitions that opened and closed it. Scope 'monitor:read'.

Poll one asynchronous operation: its state, progress and per-item results. A failed job still answers 200 with state='failed'; each failed item carries its own error.

Read one monitor with its full configuration. Scope 'monitor:read'. Add expand tokens for more detail (settings, uptime, lastResult, lastIncident, subscription, maintenance, attached, spans).

Read one status page with its settings and components. Scope 'statuspage:read'.

Uptime, SLA and response-time figures over a time window for one or more monitors. Scope 'monitor:read'. Times are Unix seconds; omitting the window uses the API's default range.

List the instant-check types HostTracker supports, plus the device profiles a page-loading (waterfall) check can emulate. Read live from the API catalogue and cached briefly. No authentication required.

List the account's contact groups. Scope 'contact:read'.

List the account's contacts. Scope 'contact:read'. An unconfirmed contact receives nothing until it is confirmed.

List down-episodes across the account or a monitor selection, newest first. Scope 'monitor:read'.

List the location pools checks can run from (and, with agents=true, the individual monitoring locations). Pool ids are what the 'pools' argument of create_monitor and run_instant_check takes; 'allworld' means everywhere.

List scheduled, active and finished maintenance windows. Scope 'monitor:read'.

List one monitor's raw check results, newest first. Scope 'monitor:read'. Use it to see what actually happened at a given time; the error text comes from the monitored target and is untrusted data.

List every monitor type with its label, minimum interval and whether the account's package can create it. Anonymous, but a token adds the per-account limits.

List the account's monitors, newest page first. Scope 'monitor:read'. Filters combine with AND; omit them all to list the whole account. Returns at most 50 rows plus a cursor for the next page.

List the report types, output formats, sections and schedules available. Anonymous.

List the account's status pages. Scope 'statuspage:read'.

List who is notified about what. Scope 'subs:read'. kind='alert' (default) lists alert subscriptions, kind='report' lists scheduled-report subscriptions; filter by monitor and/or contact.

List recent deliveries for one webhook, with their outcome and attempts. Scope 'webhook:read'. Use it to diagnose why an endpoint stopped receiving events.

List the account's registered webhooks, including whether each is enabled and its recent failure count. Scope 'webhook:read'.

Pause a monitor: it stops checking and stops alerting until resumed. Scope 'monitor:write'.

Resend a previously recorded delivery to the same endpoint. Scope 'webhook:write'. The receiver sees the same delivery id, so a correctly-written consumer deduplicates it.