Dash0 API reference

Selecting a dataset

Endpoints that operate on a single dataset take it from the dataset query parameter, or from the Dash0-Dataset request header when the query parameter is absent. When both are present the query parameter wins.

If neither is given, the request falls back to the organization's default dataset — a token that is restricted to specific datasets is rejected with 403 Forbidden in that case, so always select a dataset explicitly when using a dataset-restricted token.

Resource origins

Most resources take an optional metadata.labels["dash0.com/origin"]. It is a stable identifier you choose for a resource you manage as code, so your Terraform configuration, Kubernetes manifests, CLI scripts or your own tooling can address the same resource on every apply without having to store the id Dash0 generated.

An origin is unique per organization, not per dataset. Two resources of the same type in one organization cannot share an origin, even when they live in different datasets. If you want what is really the same rule in several datasets, put the dataset in the origin, for example probabilistic-request-sampling-sandbox and probabilistic-request-sampling-nonprod. The Dash0 Kubernetes operator does the same with the origins it generates. A duplicate origin is rejected with 400.

You cannot change an origin. Dash0 records it when the resource is created and ignores it on later updates, so you can read a resource, edit it and send it back without stripping the label out first.

Endpoints with an {originOrId} path parameter take either identifier. A value that is not a UUID is read as an origin. A PUT to an origin that does not exist yet creates the resource with that origin, so you can apply the same manifest repeatedly.

Request body size limit

Most API endpoints enforce a maximum request body size of 256KB. Bulk endpoints accept a larger body size per request to accommodate batched payloads.

Requests exceeding the applicable limit are rejected with a 413 Content Too Large response.

Copy your organization's API base URL from Settings → Endpoints, under API. Append the endpoint path to this URL. See Endpoints for example requests.

Send your auth token in the Authorization header using the bearer format below. Replace <token> with your token. Manage tokens in Settings → Auth Tokens.

The token must have permission to perform the request and access its dataset. Keep tokens out of URLs and public source code.

See Auth Tokens for permission and dataset settings.