Try everything, change nothing.
There's no separate test server: these are the ways to use the real API without touching anyone's sites, from no key at all to a key that can only read.
With no key: the public API
The public status pages' numbers, with no sign-up. Nothing here can change anything.
curl https://sitesinthewoods.com/api/public/sites
60 requests a minute per address, with the same RateLimit fields, errors and next_steps as every other route, so what you build against it works the same with a key.
With a viewer key: read-only
A viewer key reads a team's own sites and can't write: a POST with it is refused (forbidden) before anything happens. It's the safe key to give an agent you're trying out. Creating one.
Try it: a journey that leaves nothing behind
On a journey's form, Try it runs the journey once against your site and shows the result. It writes no run, no status, no incident and no saved account, though its cost counts toward the journey spend cap.
What a write does, and how to undo it
- Writes act on the team's real sites: dismiss, check again, maintenance windows, pause, journey runs. Each is recorded in the team's activity log.
- Every write is idempotent and takes an
Idempotency-Key: a retry with the same key gets the first answer and does nothing more. - Each one has its opposite: end the maintenance window, resume the paused site, undismiss the incident.
- Run now queues a real journey run, which spends from the team's journey cap; it answers 202, and you check on it.
What there isn't
A separate test team or test server. If you need one, tell us.
Last updated .