Locations
List the probe locations you can attach to a monitor.
The location object:
{
"id": "9f31c2ab-…",
"object": "location",
"name": "Stockholm, Sweden",
"city": "Stockholm",
"region": "Europe",
"country": "Sweden",
"country_code": "SE"
}List locations
GET /v1/locations — the full public catalog of probe locations. Use the
id values in the locations array when
creating or
updating a monitor.
curl https://watchfor.io/api/v1/locations \
-H "Authorization: Bearer wf_live_YOUR_KEY"{
"object": "list",
"data": [ { "id": "9f31c2ab-…", "object": "location", "…": "…" } ],
"has_more": false
}How many locations a single monitor may use — and which scheduling strategies are available — depends on your plan; the limit is enforced when the monitor is created or updated, with a clear error message if the selection doesn't fit.
Monitor types reference
Every WatchFor monitor type — its target format, default alert rules, all alert metrics you can build rules from, and every config field. The complete per-type reference for building monitors and alert rules via the API.
Incidents
List incidents and drive their lifecycle — acknowledge and resolve — from your own tooling.