Every way in, and what each one opens.
The Sites in the Woods API is JSON over HTTPS. The public sites' stats need no key; a team's own sites need a key from that team. Every route below is also an MCP tool.
Try it with no key
curl https://sitesinthewoods.com/api/public/sites curl https://sitesinthewoods.com/api/public/sites/SITE-SLUG
The same numbers as the public status pages, limited to 60 requests a minute per address. Nothing you call this way can change anything: see the sandbox.
Authentication
An admin creates a key on the team's API keys page; it's shown once. Send it as a bearer token, and keep it in the environment, never in a command or a chat:
export SITES_IN_THE_WOODS_API_KEY=sm_… curl -H "Authorization: Bearer $SITES_IN_THE_WOODS_API_KEY" https://sitesinthewoods.com/api/status
Viewer keys read; dismiss, check again, maintenance windows, pause, journey runs need a member or admin key, on teams with 10 sites or more. How keys work.
Endpoints
GET /api/status: Every one of the team's sites: its status right now, and the open incidents. Any key.GET /api/sites: The team's sites: status, homepage uptime over 1, 7 and 30 days, open incidents. Any key.GET /api/sites/:slug: One site: its last 7 days (as in the weekly brief), open incidents, domain and TLS expiry. Any key.GET /api/sites/:slug/insights: One site's daily insights: page weight, security headers, prefetches, page errors, broken links, cache, dead ends. Any key.GET /api/sites/:slug/scans: One site's API recovery scans, newest first: state, how each ended, and findings by weight. Any key.GET /api/sites/:slug/scans/:id: One API recovery scan: what it saw, its findings, the fixes and what changed since the last scan. Any key.GET /api/sites/:slug/maintenance: One site's maintenance windows: on now, scheduled, and the last 30 days. Any key.GET /api/sites/:slug/map: One site's structure from its sitemaps: sections, new and removed pages, what fails. Any key.GET /api/sites/:slug/events: What changed on one site: incidents opened and resolved, code pushes, maintenance, new pages. Any key.GET /api/incidents: Incidents, open now or recent; open outages and slowdowns carry the likely cause. Any key.GET /api/incidents/:id: One incident in full: an outage's whole diagnosis, where it was seen and how it failed. Any key.GET /api/domains: The team's domains: registration expiry, registrar, nameservers, status. Any key.GET /api/public/sites: Every public site's status and uptime, no key needed. No key.GET /api/public/sites/:slug: One public site's 90 days: daily uptime, response time and outages, no key needed. No key.POST /api/incidents/:id/dismiss: Dismiss an open incident as noise. A key that may write.POST /api/incidents/:id/undismiss: Bring back a dismissed incident. A key that may write.POST /api/incidents/:id/recheck: Check an incident again now. A key that may write.POST /api/sites/:slug/maintenance/start: Start a maintenance window on a site now. A key that may write.POST /api/sites/:slug/maintenance/end: End a site's maintenance windows now. A key that may write.POST /api/sites/:slug/pause: Pause a site's checks. A key that may write.POST /api/sites/:slug/resume: Resume a paused site's checks. A key that may write.GET /api/sites/:slug/journeys: A site's agent journeys: what each asks an agent to do, its model and schedule, and its latest verdict. Any key.GET /api/sites/:slug/journeys/:journey/runs: A journey's runs, newest first: verdicts, where they got stuck, costs and outcome checks. Any key.GET /api/sites/:slug/journeys/:journey/runs/:id: One journey run, step by step: what the agent thought, fetched, got back and why it stopped. Any key.POST /api/sites/:slug/journeys/:journey/run: Run a journey now, as a job. A key that may write.GET /api/sites/:slug/journeys/:journey/requests/:id: A journey run asked for with Run now: queued, running or finished, and its verdict. Any key.
Every parameter and response field: the reference (also as Markdown), and the OpenAPI 3.1 description.
Example requests
One site's last week, its incidents, domain and certificate:
curl -H "Authorization: Bearer $SITES_IN_THE_WOODS_API_KEY" https://sitesinthewoods.com/api/sites/SITE-SLUG
Hold a site's alerts for a deploy (a write), safe to retry with the same Idempotency-Key:
curl -X POST -H "Authorization: Bearer $SITES_IN_THE_WOODS_API_KEY" -H "Idempotency-Key: deploy-2026-11-19-1" -H "content-type: application/json" -d '{"minutes": 30, "reason": "deploy"}' https://sitesinthewoods.com/api/sites/SITE-SLUG/maintenance/start
Run a journey now (a job: the answer is 202, with where to check on it):
curl -X POST -H "Authorization: Bearer $SITES_IN_THE_WOODS_API_KEY" https://sitesinthewoods.com/api/sites/SITE-SLUG/journeys/JOURNEY/run
Answers, errors and limits
- A success is
{"data": …}withnext_steps, the calls that usually come next. - An error is RFC 9457 problem details with a code to branch on and what to do next: every code.
- Requests a minute per key, by the team's sites: 60 on the free site, 300 from 2 sites, 1,000 from 25; writes 10 in 10 seconds. Every answer says what's left in
RateLimit-PolicyandRateLimit. - The API is version 1: every answer says so in an API-Version header, and a request may send API-Version: 1 to pin it (any other value is refused, so a client never gets a version it didn't ask for). Version 1 changes only by adding routes and fields; one that has to go is announced at least 90 days ahead, on its responses, with Deprecation (RFC 9745) and Sunset (RFC 8594) headers and a Link to /developers#versioning (rel="deprecation"). A change that removes or renames anything would be a new version, chosen with this header, with version 1 kept alongside it.
MCP, the CLI and skills
- The hosted MCP server,
https://sitesinthewoods.com/mcp, has one tool per endpoint and takes the same key: setting it up. - The CLI and SDK,
npx sites-in-the-woods: its commands. - Agent skills for the jobs these routes do.
Everything for developers and agents in one place: Developers.
Last updated .