Getting Started

Endpoint Structure

An API endpoint typically consists of:






is v1


is either grid, timeseries or station, see Types


is either historical, current or forecast, see Modes


is one of the resources listed in Resources.


Not for every permutation of type, mode and resource_id exists an endpoint.

All datasets can be listed via

Furthermore, all endpoints metadata can be requested by appending /metadata.


In this example we want to get the current air temperature from the TAWES station WIEN/HOHE WARTE.

From we know the endpoint

will provide the data. The endpoint requires request parameters parameters and station_ids. From the metadata

we find the parameter name TL for air temperature and station_id 11035 for WIEN/HOHE WARTE. This results in:

parameters and station_ids are array types. You can pass multiple values either as a comma-separated string, e.g. parameters=TL,TLMAX or you pass the query parameter multiple times, e.g. parameters=TL&parameters=TLMAX


If you prefer to use Swagger to understand the API capabilities, see OpenAPI docs

Further information

User Guide:

User Guide.

Data Portal:

Graphical user interface.

List all endpoints:

API endpoint listing all available dataset endpoints.

OpenAPI docs:

API endpoint documentation.