Sites in the Woods

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

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

MCP, the CLI and skills

Everything for developers and agents in one place: Developers.

Last updated .