Authentication boundary
Most API actions require an authenticated StatusIntel session. Public status-page reads are intentionally separate from account actions. Keep automation tied to least privilege, and do not expose session cookies or internal credentials in client-side code.
Endpoint categories
| Category | Purpose |
|---|---|
| Monitor APIs | List monitors, load dashboard state, read charts, and inspect recent check history. |
| Organization APIs | Manage organization settings, invitations, members, roles, and groups. |
| Status page APIs | Publish selected monitor state to a customer-facing status page. |
| Authentication APIs | Handle login, logout, registration, and two-factor authentication flows. |
Public status page reads
Public status pages use safe read endpoints so customers can view service health without signing in. Administrative status page changes stay behind account authentication.
Automation guidance
For operational automation, prefer purpose-built endpoints and short-lived credentials when available. Avoid scraping dashboard HTML for state. If a route changes for a product reason, API-oriented integrations should continue to use documented boundaries rather than page layout details.
This public overview avoids listing sensitive internal routes. Contact support if you need a specific integration pattern reviewed.