API

All the data is free to read as JSON, with no key and no sign-up: plain files on https://liftradar.eu, readable from any site (CORS allows any origin). The format is defined by the JSON Schema of each file.

For code generators and API tools, every file is described in OpenAPI 3.1.

• All resorts
• One resort
• History
• Stats
• Pistes and lifts
• MCP
• Reading the values
• Polling

All resorts

GET https://liftradar.eu/json/index.json

Every resort with its main values: status, snow depths, open lifts and slopes, avalanche level and location (schema). Each resort's country and id give the address of its full report.

One resort

GET https://liftradar.eu/json/<country>/<id>.json

One resort's full report (schema): everything in the list, plus snow stations, lifts by type, slopes by difficulty, the avalanche bulletin and the reports it was built from. For example json/at/hintertux.json. The id is in the address of each resort's page on this site.

country is the ISO code in lower case: at, ch, cz, de, es, fi, fr, it, no, pl, sk. These addresses stay: when resorts merge, the old ones keep working as copies of the new one's.

curl -s https://liftradar.eu/json/at/hintertux.json | jq '{status, snow: .snow.mountain_cm, lifts}'

History

GET https://liftradar.eu/history/<country>/<id>.json

The key numbers of every run over the last 365 days, one list per value: time, status, open and total lifts and slopes, open km and snow depths (schema). Data has been collected since 24 October 2026.

Stats

GET https://liftradar.eu/json/stats.json

Daily totals per country and region over the last 365 days: resorts tracked and open, and their open lifts, slopes and km (schema).

Pistes and lifts

GET https://liftradar.eu/ski/v1/10/<x>/<y>.json
GET https://liftradar.eu/ski/v1/resorts.geojson
GET https://liftradar.eu/ski/v1/meta.json

The lifts, pistes and ski areas of OpenSkiData in map tiles (XYZ, zoom 10), each with its resort here when it has one (schema), and each resort's outline and point on the map. The build and counts are in meta.json. Rebuilt weekly, under the ODbL: data from OpenSkiData, © OpenStreetMap contributors.

MCP

https://liftradar.eu/mcp

For AI assistants, the same data is an MCP server, with no key: add the address above as a remote server (Streamable HTTP) in Claude, Cursor or any other MCP client. Its tools find resorts by country, status, snow, open lifts or distance from a point, and read one resort's report, its history and the daily stats.

claude mcp add --transport http liftradar https://liftradar.eu/mcp

Reading the values

• null means the source doesn't publish the value. status is never null: it's open, closed or no_report.
• With no_report, lifts.open is 0 and slopes.open is null. With closed, the snow depths and condition are null; last_snowfall and station measurements stay.
• fetched_at is when we read the report and lifts_updated_at is the resort's own report time, null if its source has none. status_from is set when the latest run couldn't read the report, and gives the time of the run the values come from.
• Times are ISO 8601 with the Vienna offset. condition is in the source's language.

What the numbers mean, and where they can mislead, is on About the data.

Polling

The data changes twice a day, at about 08:40 and 13:40 Vienna time, so there's no point reading it more often than hourly. The files have an ETag: send If-None-Match and an unchanged file costs nothing. Questions, or a use we should know about: miron [at] liftradar.eu.