Skip to main content
The StatusStack API is a REST interface over JSON. Use it to manage stacks, sources, uptime monitors, incidents, and related resources from your own tools. Base URL: https://statusstack.com/api Versioned operations live under /v1. A few unversioned routes (/health, /api-keys, /sso/discover) sit directly on that base.

​
Authenticate

Send an API key as a Bearer token. Keys are created in the dashboard under Settings → API Keys, and most v1 operations require a key scoped to a team.

Authentication

API key permissions, team scope, and MCP credentials.

​
What is documented

This reference is generated from the OpenAPI contract (openapi/api-docs.yaml, v1.4.0). Only the operations documented here are part of the supported public API; any other endpoint is unstable and may change without a version bump. Documented groups include:
  • Stacks — create, update, attach sources and components, export configuration
  • Sources — catalog and custom sources, components, analytics
  • Website monitors — URL health checks, pause and resume
  • Incidents — list, detail, history, and updates
  • Status overrides and provider impact advisories
  • API keys, tags, and categories
  • MCP — manifest, JSON-RPC messages, tools, and resources
/v1/tickers still works as a deprecated alias of /v1/stacks. Use the stacks paths.
Operations such as activity log, AI summaries, dependencies, and the newer /v1/monitors family exist in the product but are not yet in this contract. Treat them as unstable until they appear here.

​
Conventions

Request and response bodies are JSON unless an export returns CSV. Always use HTTPS.
List endpoints that paginate accept page and per_page (default 15, maximum 100 on stacks).
Resource IDs are UUIDs. Path parameters use names such as stack_id, source_id, and monitor_id.
Versioned v1 operations share a 120 requests per minute limit and return 429 with Retry-After. See Rate limits.
Authentication failures and missing API-key permissions return { "error": "..." }. Most other failures return { "message": "..." } and may include errors. See Errors.

​
Try an endpoint

The pages in this tab include an interactive playground. Create a key, then list the stacks in that team: