Can you use a UptimeScout incidents response to announce immediately that a service is down? No: this endpoint lists services with recently elevated disruption signals, and the specification explicitly notes that these are not provider-confirmed incidents. The practical result is a short list of signals to investigate, not a definitive conclusion about the cause of an outage.

This distinction is useful for on-call engineers and analysts: an automated alert can say “check service X in region Y” while leaving confirmation of the event and explanation of its cause to the provider’s official status information or your own diagnostics. The UptimeScout specification documents separate routes for signals, current status, and observation history.
What the signal list returns
/v1/incidents is a GET endpoint for a catalog of services with elevated disruption signals. Its parameters include filters for service, region, category, search query, and time window. A license is required for the response; the API describes Bearer-token authentication. The region field accepts a two-letter code, and hours sets a window from 1 to 2160 hours.
The word “incident” in the path is easy to read as “confirmed outage,” but the documentation defines it more narrowly: a recent observation signal. So phrase alerts according to the response data—for example, “an availability disruption signal was detected”—and don’t attribute an acknowledgment of an incident to the service provider.
Basic checks before sending an alert
First, save the original response along with the time it was received and the request parameters. Then check which service and region were returned, and assess freshness using the service fields observed_at and stale. If an observation is marked stale, separate it from the current signal rather than presenting it as the state “right now.”
curl -sS 'https://api.uptimescout.com/v1/incidents?region=US&hours=24' \
-H "Authorization: Bearer $UPTIMESCOUT_LICENSE_KEY"
This example queries the United States over a 24-hour window; the key is read from an environment variable and is not printed on the command line. After receiving the response, check for HTTP errors and validate the JSON structure, then process each returned service separately. The schema’s status values include operational, degraded, outage, and unknown; if a field or value is missing, don’t substitute your own interpretation.
For a signal that requires action, request the corresponding service’s current status through /v1/status and its history through /v1/history. In the history, it is useful to retain resolution_seconds, samples, counts, and effective_start alongside the time series: this lets analysts see the temporal resolution of the data and the actual interval available. The specification warns that missing intervals are unknown; an empty gap cannot automatically be treated as either availability or an outage.
How to turn the response into a verifiable report
For each record, create fields for the service ID and name, request region, status, observation time, staleness flag, response-received time, and a link to the official status source if the team has checked it. Your integration or operator fills in the last field: the UptimeScout specification does not promise that a signal includes a confirmed cause or a provider statement.

Divide the workflow into three states. “Signal received” means that a record appeared in the /v1/incidents results. “Status being checked” means that you requested the current status and history. Reserve “Confirmed” for a conclusion supported by an external official statement or an internal check. This simple distinction prevents a dashboard from presenting an aggregated signal as an established fact.
If the team is building a report across multiple regions, make separate requests using the required region codes and save the parameter with each result. The lang field applies to service descriptions; it does not change the observation region. This distinction matters when comparing, for example, a localized catalog with regional status.
Where conclusions end
The verifiable output of this workflow is a signal log with explicit timestamps, region, and freshness indicators, supplemented by a separate check of status and history. It helps identify what needs attention and what could be confirmed using the chosen sources. The /v1/incidents response itself reports an elevated observation signal; confirming an outage requires supporting data.