Fnugg API documentation (v1)

Norsk: Vi ønsker alle skiinteresserte velkommen til å benytte seg av fnuggs åpne API. Det er ikke lov til å bruke våre data i tjenester som tilsvarer fnugg.no. Når du bruker vårt API må du alltid opplyse at informasjonen er hentet fra fnugg.no, enten i tekstform eller ved bruk av vår logo. Informasjonen som kan hentes ut gjennom fnuggs åpne API er beskyttet av åndsverkslovens bestemmelser. Vi kan når som helst trekke tilbake samtykket til bruk.

English: All skiing enthusiasts are welcome to use the open API of "fnugg". The use of our data in services that are essentially identical to fnugg.no is not allowed. When using our open API, you must inform your users that the information comes from fnugg.no, by text or by using our logo. The information obtainable from the API is protected by law. We may withdraw our consent to use the API at any time.

---

Available endpoints

Search

• /search - Advanced search across resorts, articles, regions, and resort types with extensive filtering options

Get resources

• /get/resort/{id} - Get a specific resort by ID
• /get/blog_post/{id} - Get a specific article/blog post by ID
• /get/region/{id} - Get a specific region by ID
• /get/resort_type/{id} - Get a specific resort type by ID

Geographic services

• /geodata/getnearest - Find resorts nearest to geographical coordinates
• /geodata/getdistance - Get distance and duration between two locations

Suggestions

• /suggest/autocomplete - Get autocomplete suggestions for resort search

---

Interactive playground

Try the API directly in your browser →

---

Common features

Response format

All endpoints return JSON responses following ElasticSearch-like structure with _index, _type, _id, and _source fields for individual resources.

Source field filtering

Most endpoints support sourceFields parameter to return only specific fields from the _source object using dot notation (e.g., sourceFields=name,location.lat,location.lon).

Error handling

The API returns appropriate HTTP status codes:

• 200 - Success
• 400 - Bad Request (missing/invalid parameters)
• 404 - Resource Not Found
• 500 - Server Error

Common use cases

1. Search for open ski resorts: Use /search with type=resort, facet=resort_open:1, and powderAlarm=true for fresh snow
2. Get resort details: Use /get/resort/{id} to fetch complete information about a specific resort
3. Find nearby resorts: Use /geodata/getnearest with lat/lon coordinates
4. Autocomplete search: Use /suggest/autocomplete for typeahead functionality
5. Search articles: Use /search with index=blog and type=blog_post

Weather icons/IDs

On every resort page there is a weather icon and a textual representation showing the current weather state at the resort. What decides the icon and the text is taken from the field fnugg_id which is found in the resort JSON in the conditions.combined node. The IDs go from 1-9, and represent the following states:

ID	Weather type
1	Strålende sol
2	For det meste sol
3	Overskyet
4	Her er det meldt snø
5	Det snør!
6	Fare for regn
7	Det regner
8	Fare for sludd
9	Det sludder..

The icons used can be downloaded here.

All icons start with resort-weather-X, where X represents the fnugg_id. On Fnugg, we use the white icons, but in the zip there is also included a blue lined version if you intend to use the icons on a white background.

Example of fetching the weather

Note that some resorts have both top and bottom weather reports. For those with only one report, the fnugg_id will be found in the top node.

Example of only one weather report (Storefjell Skisenter, Golsfjellet): /get/resort/41?sourceFields=name,conditions.combined.top.symbol.fnugg_id

Example of two weather reports (SkiStar Trysil): /get/resort/2?sourceFields=name,conditions.combined.top.symbol.fnugg_id,conditions.combined.bottom.symbol.fnugg_id