Tools
API
Everything the dashboard does goes through one documented REST API (OpenAPI 3.1). One page per area, with every operation.
| Area | What it does | Operations | Minimum role |
|---|---|---|---|
Status pagesstatus-pages | Create, publish, rename, brand and archive status pages. | 8 | Viewer reads; admin writes |
Componentscomponents | Add components to a page, set their baseline status and read their history. | 7 | Viewer reads; admin writes |
Incidentsincidents | Open incidents, mark affected components and post updates until resolved. | 5 | Viewer reads; admin writes |
Maintenancemaintenance | Schedule, edit, start, complete and cancel maintenance windows. | 7 | Viewer reads; admin writes |
Subscriberssubscribers | List subscribers with masked addresses, reveal one or delete one. | 3 | Admin |
Audit logaudit | Read who changed what in your organization, and when. | 1 | Admin |
Onboarding and membersonboarding | Create or join an organization, review join requests and manage members. | 11 | Any signed-in user |
Current userme | Who is signed in, and which organization and role they have. | 1 | Any signed-in user |
Public status APIpublic | Read a published page, its history and feed; subscribe and unsubscribe. | 6 | None (public) |
The /api/* operations accept sign-in tokens from the uptimeloom dashboard only; personal API keys and an MCP server for assistants are not available yet. The public status API needs no token.