Skip to Content
Public APIOverview

Ullr Public API

The Public API serves the same data your crews maintain in Ullr: areas, trails, lifts, terrain park features, and the updates your team posts through the day. It is a read-only JSON API over HTTPS, authenticated with an API key.

If you only want live conditions on your website, you probably do not need this API at all — the embeds render it for you with a script tag and no code. Reach for the API when you need the raw data: a custom conditions page, a mobile app, a lift-status sign, a data warehouse, or a partner feed.

Base URL

https://api.ullr.ski/public/v11

Every request needs an api-key header:

curl -H "api-key: $ULLR_API_KEY" \
  "https://api.ullr.ski/public/v11/SNOW/areas/your-area-id/trails"

What you can read

ResourceEndpointWhat it gives you
Areas/{sport}/areas/{areaId}Resort name, location, sports, settings, summary counts
Trails/{sport}/areas/{areaId}/trailsTrail status, surface conditions, difficulty, length
Lifts/{sport}/areas/{areaId}/liftsLift status, type, carrier capacity, vertical
Features/{sport}/areas/{areaId}/featuresTerrain park jumps, rails, boxes and their status
Updates/{sport}/areas/{areaId}/updatesPark reports and updates, newest first, paginated

Trails, lifts and features each also have a /history variant that answers “what did this look like at 9am on Saturday” — see Conventions.

The API is read-only. There are no POST, PUT or DELETE endpoints: data is written by your crews in the Ullr apps.

Getting access

API keys are created per area, in the Ullr dashboard under Integrations → API keys. You need the apiKeys:create permission at that area — usually an admin or manager role.

  1. Open Integrations → API keys  in the Ullr dashboard.
  2. Create a secret key for server-side use, or a publishable key if the key will be visible in a browser.
  3. Pick the scopes it needs. Start narrow — you can always add more.
  4. Copy the key. Secret keys are shown once and cannot be retrieved later.

Full detail, including the two key types and how domain restrictions work, is in Authentication.

Where to go next

Key types, scopes, and the api-key header.

Authentication

Versioning, sports, errors, caching, pagination and history.

Conventions

Every endpoint, parameter and response field.

Endpoint reference

OpenAPI 3.0.3, for generating clients.

OpenAPI spec

Pages below this one are for Ullr customers and partners, so they ask you to sign in with your Ullr account first. If you do not have one, get in touch.

Authentication