Manage it in code
The REST API covers monitors, incidents, on-call, status pages and more, with an OpenAPI spec for generating clients.
Monitoring that fits your stack. Manage monitors through the API, route alerts to the tools your team uses, and send events to your own endpoints.
Free tier included. No credit card required.

Keep your monitoring close to the rest of your workflow. Start with a notification channel, then automate the parts that repeat.
The REST API covers monitors, incidents, on-call, status pages and more, with an OpenAPI spec for generating clients.
Route notifications to Slack, Discord, Microsoft Teams or Telegram, alongside email and other supported channels.
Send signed JSON events to your own HTTPS endpoint, with automatic retries and a delivery log.
Build around your monitoring, not around another manual checklist.
Create and update monitors from a deploy script or internal tool, so monitoring keeps pace with the services you run.
Generate a client from the OpenAPI spec, or call it with curl.
Connect a supported channel and assign it to a notification group. Keep alerts close to the conversations where your team responds.
One alert reaches every channel in the group.
Send events to your own HTTPS endpoint when your workflow needs a custom handler. Every delivery is signed, so your receiver can verify where it came from.
Failed deliveries are retried automatically, and the delivery log shows each attempt.
Slack, Microsoft Teams, Discord, Telegram, Google Chat and Mattermost. Alerts can also go to PagerDuty, Opsgenie, Pushover, SMS and email.
Yes. Call the REST API from your tool, with the reference and an OpenAPI spec at docs.siteqwality.com, and send alerts to it with a signed webhook.
Each API key can make 600 requests a minute, and the MCP server allows 300 a minute per key or user. Responses tell you how many requests are left this minute.