WEATHER API / REFERENCE

Full API
reference.

All endpoints, query parameters, and rules for working with the published forecast.

AUTHENTICATION

One key for every request

Create an API key in your account and send it in the request header. The key secret is shown only once.

HTTP

Authorization: ApiKey eol_your_secret_key

ENDPOINTS

Three core requests

GET/api/v1/metadata/

Dataset version, available parameters, coverage, forecast period, and source attribution.

GET/api/v1/point/

Parameter values at one location for an exact timestamp in the published forecast.

GET/api/v1/series/

A time series for one location with pagination.

QUERY PARAMETERS

What to send in a request

Parameter	Used by	Description
`latitude`	point, series	Latitude in degrees, from −90 to 90.
`longitude`	point, series	Longitude within the published dataset coverage.
`time`	point	An exact UTC time, for example 2026-08-03T00:00:00Z.
`start`, `end`	series	Start and end of a UTC series; both timestamps must be available in the dataset.
`parameters`	point, series	Comma-separated codes. If omitted, the API returns all available fields.
`interpolation`	point, series	`nearest` (default) or `linear` for bilinear coordinate interpolation.
`page`, `page_size`	series	Page number and page size; the maximum is 500 results.

RESPONSES AND ERRORS

How to read a result

JSON

{
  "time": "2026-08-03T00:00:00Z",
  "latitude": 55.75,
  "longitude": 37.62,
  "dataset_id": "…",
  "values": {"surface.air_temperature_2m": {"value": 281.4, "unit": "K"}}
}

400

Invalid coordinates, parameter code, or time outside the published time axis.

401

No API key, or the key is invalid or revoked.

429

The key's short-term request limit has been exceeded.

Open interactive Swagger ↗