EnoughStack
Status

Monitor websites and services, track incidents and share system health.

Status API

Manage monitors, incidents, maintenance windows and your public status page from your own code.

Getting started

Create monitors and keep incidents and planned maintenance in sync with your own systems.

Create a website monitor
curl -X POST https://enoughstack-app-7r9ib.ondigitalocean.app/api/public/v1/status/monitors \
  -H "Authorization: Bearer $ENOUGHSTACK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name": "Website", "target": "https://example.com/health",
       "interval_seconds": 300, "public": true}'
Open an incident
curl -X POST https://enoughstack-app-7r9ib.ondigitalocean.app/api/public/v1/status/incidents \
  -H "Authorization: Bearer $ENOUGHSTACK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"title": "API slowdown", "monitor_ids": ["mon_123"],
       "message": "Investigating elevated latency", "severity": "major", "published": true}'

Replace the example monitor id with one returned by the API. Publish the status page with PUT /status/page to share public monitors and incident updates. Uptime reflects observed checks.

Status monitors

  • GET/status/summaryObserved health, uptime and recent incidentsstatus:read
  • GET/status/monitorsPage through monitorsstatus:read
  • POST/status/monitorsCreate an HTTP, TCP or heartbeat monitorstatus:write
  • GET/status/monitors/{monitor_id}One monitor with checks and incidentsstatus:read
  • PUT/status/monitors/{monitor_id}Replace a monitor's settingsstatus:write
  • DELETE/status/monitors/{monitor_id}Delete a monitorstatus:write
  • POST/status/monitors/{monitor_id}/pausePause checks for a monitorstatus:write
  • POST/status/monitors/{monitor_id}/resumeResume a paused monitorstatus:write
  • POST/status/monitors/{monitor_id}/checkQueue a check for a monitorstatus:write

Status incidents

  • GET/status/incidentsPage through incidentsstatus:read
  • POST/status/incidentsOpen an incident, optionally on the public status pagestatus:write
  • GET/status/incidents/{incident_id}One incident and its updatesstatus:read
  • POST/status/incidents/{incident_id}/updatesPost an update or resolve an incidentstatus:write

Status maintenance and page

  • GET/status/maintenancePage through maintenance windowsstatus:read
  • POST/status/maintenanceSchedule a maintenance windowstatus:write
  • DELETE/status/maintenance/{window_id}Delete a maintenance windowstatus:write
  • GET/status/pagePublic status page settingsstatus:read
  • PUT/status/pageReplace the status page title, description, monitors and publication statestatus:write

API keys

Workspace requests carry a key with the specific permission listed for each action. Create keys, narrow existing permissions and set expiration under Developers. Full keys are shown once.

Manage API keys

Interactive docs

Every endpoint with request and response schemas, generated from the API itself. Use “Authorize” with one of your keys to try requests.

Open API docs

Conventions

Scopes
OpenAPI marks each authenticated operation with x-required-scope, such as email:draft, email:send or inbox:reply. A key needs the permission listed for that operation.
Errors
Always {"error": {"code": "...", "message": "..."}}. Codes include unauthenticated, insufficient_scope, not_found, validation_error.
Pagination
Lists return paging.next; pass it back as starting_after. Up to 100 items per page.
Operation outcomes
Mutations return X-Operation-ID and Operation-Location headers. Follow the operation URL to inspect progress, errors and the resulting resource. Provider accepted means a provider accepted the request; delivered requires delivery evidence.
Webhooks
Queued deliveries run in the background with signed HTTPS requests and retries. Delivered means the endpoint returned a successful HTTP response. Unknown means acceptance could not be confirmed; simulated means no request was sent. Receivers should deduplicate by event ID.
Versioning
The version is in the path (/v1). Fields are only ever added.

Recorded webhook delivery

{
  "id": "dlv_001",
  "webhook_id": "wh_001",
  "event": "contact.created",
  "event_id": "evt_001",
  "status": "queued",
  "response_code": null,
  "duration_ms": null,
  "attempt_count": 0,
  "max_attempts": 5,
  "payload": {
    "id": "ct_0231",
    "list_id": "lst_audience",
    "email_address": "maya@northwind.studio",
    "status": "subscribed",
    "tags": ["customer", "team"]
  },
  "at": "2026-10-06T09:14:02Z"
}