Retrieve the synthetic check locations available to the organization
/api/synthetic-checks/locationsReturns Dash0 public regions and the organization's private synthetic locations as one
list. kind distinguishes them.
The id of an entry is what a synthetic check definition stores to target it: the region
identifier for a public region, and the Dash0-assigned opaque id for a private location. A
private location's customer-chosen locationId is a label only and never identifies it.
Deleted private locations are omitted.
Private locations carry health, derived from the workers currently connected to them.
health.status is unknown when Dash0 cannot determine the connection state; that is
distinct from offline, which reports that no worker is connected.
Sample request12curl --request GET 'https://api.eu-west-1.aws.dash0.com/api/synthetic-checks/locations' \--header "Authorization: Bearer ${DASH0_AUTH_TOKEN}"
Responses
The locations the organization can target.
Array items
The value a synthetic check definition stores to target this location: the region identifier for a public region, and the Dash0-assigned opaque id for a private location.
public: A Dash0-operated region, available to every organization.private: A location the organization runs itself, visible only to that organization.
"public""private"Private locations only. The label to show for the location. It is not unique, because
two of an organization's locations may carry the same value after a re-registration,
so display it alongside id when it repeats.
Private locations only. When Dash0 first registered the location.
Private locations only. Public regions are operated by Dash0 and report no per-location health here.