Overwatch API

What is Overwatch?

Overwatch is a multitenant website monitoring service. Each site installs any of four apps, and every app’s results are served over this HTTP API:

• Broken links — the core: periodically crawl the site and report broken internal and external links.
• Accessibility — a rendered axe-core scan with a 0–100 score, WCAG coverage, and compliance mapping.
• Uptime — monitors probed from four regions, with incident-based uptime reporting and alerting.
• Performance — real-user Core Web Vitals from the Chrome UX Report, with regression alerts.

It is CMS-agnostic by design. The intended consumers are editorial integrations inside CMSes like Umbraco and Sanity — Overwatch is the backend service, and the CMS surfaces the reports to editors. Results can also fan out as notifications (email + chat webhooks) and as a branded stakeholder report (PDF).

Multitenant

Every request is scoped to the organization (tenant) your credentials belong to. You only ever see your own organization’s sites and reports.

A stable contract

The API is a public contract for third-party integrations: stable shapes, explicit errors, and versioned under /v1.

Authenticate

CMS integrations send an organization-scoped key in the x-api-key header; the dashboard uses a session. See the Authentication guide.

Browse the endpoints

Register sites, trigger crawls, pull reports for all four signals, manage monitors, keys, and members, and read usage in the API Reference.

Understand the crawler

What gets crawled, how scheduling and politeness work, and what counts as a broken link — in the Crawl behavior guide.

Quotas & billing

Per-app allowances, pause-by-default overage, and the immutable usage ledger — in the Quotas & usage guide.