Status pages API

A status page shows the health of your services to your users. Use this API to set up pages and components, and to link each component to the monitor that sets its status.

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.

The slug sets the public page URL, https://squasher.ai/status/<slug>. A slug has lowercase letters, numbers, and single hyphens, with at most 100 characters, and it cannot look like a page ID. Slugs are unique across Squasher. A create or update with an invalid slug returns 422. A slug that another page uses returns 409. A create above the plan’s status page limit, or with a setting the plan does not include, returns 403. See plan limits.

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.

Start here

Resources

Page operations

Component operations

CLI and MCP

Agent handoff

​Page operations

​Component operations

​CLI and MCP

​Agent handoff

Page operations

Component operations

CLI and MCP

Agent handoff