API documentation

List every monitor in your organization, oldest first. Each monitor includes id, name, type, status, enabled, target, intervalSeconds, and check timestamps. Disabled monitors report their status as paused.

A single monitor with its full config, the latest 25 checks as recentChecks, and the currently open incident as openIncident (or null). Heartbeat monitors also include their ping URL as heartbeatUrl.

Create a monitor. The config object depends on the monitor type; unlisted config fields get sensible defaults. Attach alert channels by passing channels as an array of { "channelId": "...", "notifyOn": "down" | "up" | "both" }. Returns 201 with the created monitor.

curl -X POST \
  -H "Authorization: Bearer YOUR_MAIN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Marketing site",
    "type": "http",
    "intervalSeconds": 60,
    "config": { "url": "https://example.com/health" }
  }' \
  https://infraagent.app/api/v1/monitors

Update a monitor. Send a JSON body with at least one field; anything omitted is left unchanged. Setting enabled to false pauses the monitor, true resumes it. A provided config replaces the stored config wholesale, and a provided channels array replaces all channel attachments.

Run the monitor's check immediately, outside its normal schedule, and return the result. Useful right after creating or reconfiguring a monitor.

Delete a monitor. Check history and past incidents are kept for your records, but the monitor stops running and disappears from lists immediately.

List incidents across all monitors, newest first. Each incident includes id, monitorId, monitorName, startedAt, resolvedAt, durationSeconds, cause, and lastError.

Mark an incident as acknowledged so your team knows it is being handled.

Manually resolve an open incident. Most incidents resolve themselves when the monitor recovers; use this for stragglers.

List alert channels. Channel configs hold webhook URLs and provider tokens, so the config field is only included when using a full-access key.

A single alert channel. Same key rules as the list.

Create an alert channel. Supported types: email, sms, slack, discord, telegram, pushbullet, pushover, pagerduty, zapier, splunk, and webhook. New SMS phone numbers are texted a verification code (returned as codesSentTo) and must be confirmed in the dashboard before they receive alerts.

Update an alert channel. Send at least one of type, name, enabled, config, messageTemplate. A provided config replaces the stored one wholesale.

Delete an alert channel and detach it from every monitor.

Send a sample "down" alert through the channel to confirm it is wired up correctly. Returns the delivery result, or a 400 explaining why nothing was sent.

List maintenance windows, newest first. While a window is active, matching monitors stay quiet: no alerts, no new incidents.

Schedule a maintenance window. Set monitorId to quiet a single monitor, or leave it null to quiet the whole app.

A single maintenance window.

Update a window's startsAt, endsAt, monitorId, or reason.

Delete a maintenance window. Alerts resume immediately.

List status pages with their monitor counts.

A single status page with its placed monitors in display order.

Create a status page. Plan limits on the number of status pages apply. Place monitors by passing monitors as an array of { "monitorId": "...", "displayName": "...", "sortOrder": 0 }.

Update a status page. A provided monitorsarray replaces the page's monitor placement wholesale.

Delete a status page. Its public URL stops working immediately.

List the organization's apps with their monitor counts.

Create an app. Body: name (required) and an optional slug. Creating the first real app renames the auto-created "Default" app in place, keeping its monitors.

Rename an app or change its slug.

Delete an app and everything in it: monitors, alert channels, maintenance windows, and status pages. This cannot be undone.

The organization's name, slug, and logo.

Update the organization's name or slug.

List members with their role (owner, admin, or member), name, and email.

Change a member's role between member and admin. The owner's role can't be changed.

Remove a member from the organization. The owner can't be removed.

List pending invitations, including any pre-assigned apps.

Invite people by email. Each address receives an invitation email; re-inviting a pending address resends it. Plan seat limits apply.

Revoke a pending invitation so the emailed link stops working.

Read-only plan and usage overview: plan id and name, plan limits, current usage (monitors, status pages, members), and subscription status. Plan changes go through the dashboard's billing settings.