Status Pages API - Squasher

Use the Status Pages API to configure public status pages and connect components to monitors.

Page operations

Operation	Method and path	Purpose
`statusPages.list`	`GET /v1/projects/{project_id}/status-pages`	List status pages with components and counts.
`statusPages.create`	`POST /v1/projects/{project_id}/status-pages`	Create a page with `{ name, slug, isPublic?, customDomain?, themeConfig? }`.
`statusPages.get`	`GET /v1/projects/{project_id}/status-pages/{status_page_id}`	Get one page with its components.
`statusPages.update`	`PATCH /v1/projects/{project_id}/status-pages/{status_page_id}`	Update name, slug, public state, custom domain, or theme config.
`statusPages.delete`	`DELETE /v1/projects/{project_id}/status-pages/{status_page_id}`	Delete a page, its components, and subscribers.

Component operations

Operation	Method and path	Purpose
`statusPages.listComponents`	`GET /v1/projects/{project_id}/status-pages/{status_page_id}/components`	List page components.
`statusPages.createComponent`	`POST /v1/projects/{project_id}/status-pages/{status_page_id}/components`	Create monitor, static, or group components.
`statusPages.updateComponent`	`PATCH /v1/projects/{project_id}/status-pages/{status_page_id}/components/{component_id}`	Update a component or move it into/out of a group.
`statusPages.deleteComponent`	`DELETE /v1/projects/{project_id}/status-pages/{status_page_id}/components/{component_id}`	Delete a component without deleting linked monitors.
`statusPages.linkMonitor`	`POST /v1/projects/{project_id}/status-pages/{status_page_id}/components/{component_id}/link-monitor`	Link a monitor by id or name.
`statusPages.unlinkMonitor`	`POST /v1/projects/{project_id}/status-pages/{status_page_id}/components/{component_id}/unlink-monitor`	Clear a direct monitor link by id or name.

Group components can contain child components. Static components can carry an external status URL. Monitor components roll up health from the linked monitor.

CLI and MCP

Use squasher status-pages ... and squasher status-pages components ... for terminal workflows. In MCP Code Mode, call search("statusPages"); ask before page/component writes, monitor relinking, or deletes.

Agent handoff

Review Squasher status page <status_page_id> in project <project_id>. Fetch the page and components, verify monitor links, and propose exact component changes. Do not change slugs, public visibility, custom domains, components, or monitor links without confirmation.

Related: Status pages, Custom domains.