Mammoth Mountain APImammothmountain.com ↗
Real-time trail status, snow depths, and multi-day weather forecasts for Mammoth Mountain ski resort via a simple REST API.
What is the Mammoth Mountain API?
The Mammoth Mountain API provides 3 endpoints covering live trail conditions, snow report data, and weather forecasts for Mammoth Mountain ski resort. The get_trail_status endpoint returns the full list of trails with difficulty, grooming, and open/closed status. Snow depth readings span three elevation zones, and weather data includes current conditions at base, mid-mountain, and summit alongside a multi-day forecast.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/1c9f7727-9b44-4e49-a466-2d6095434950/get_trail_status' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace mammothmountain-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Mammoth Mountain Conditions API — real-time trails, snow, and weather."""
from parse_apis.mammoth_mountain_conditions_api import (
MammothMountain,
DataUnavailable,
)
client = MammothMountain()
# Fetch trail status — all 180 trails in one snapshot.
trail_report = client.trailreports.get()
print(f"Resort: {trail_report.resort}, Total trails: {trail_report.total_trails}, Open: {trail_report.total_open_trails}")
for trail in trail_report.trails[:3]:
print(f" {trail.name} ({trail.area}) — {trail.status}, difficulty: {trail.difficulty}")
# Snow report — depths and recent snowfall at three elevations.
snow = client.snowreports.get()
print(f"\nSnow base range: {snow.snow_base_range_in} in, Season total: {snow.season_total_in} in")
print(f"Base conditions: {snow.base_conditions}")
# Weather report — current conditions and multi-day forecast.
try:
weather = client.weatherreports.get()
except DataUnavailable as exc:
print(f"Weather unavailable: {exc}")
else:
for key, condition in weather.current_conditions.items():
print(f" {condition.name}: {condition.temperature_f}°F, {condition.skies}, wind {condition.wind_speed_mph} mph")
for day in weather.forecast[:3]:
print(f" Forecast {day.day}: high {day.high_f}°F / low {day.low_f}°F, {day.snow_forecast_in} in snow")
print("\nExercised: trailreports.get / snowreports.get / weatherreports.get")
Returns the current status of all ski trails at Mammoth Mountain. Each trail includes its area, difficulty level, grooming status, and whether it is open or closed. The response is a single snapshot — no pagination or filtering. Use the trails array to build client-side filters by area, difficulty, or open/closed status.
No input parameters required.
{
"type": "object",
"fields": {
"resort": "string, resort name",
"trails": "array of Trail objects with name, area, status, difficulty, groomed, snow_making, run_of_the_day, gladed, and moguls fields",
"last_update": "string, ISO 8601 timestamp of last data update",
"total_trails": "integer, total number of trails at the resort",
"total_open_trails": "integer, number of currently open trails"
}
}About the Mammoth Mountain API
Trail Status
The get_trail_status endpoint returns a snapshot of every ski trail at Mammoth Mountain. Each object in the trails array includes the trail's name, area, difficulty, status (open or closed), and boolean flags for groomed, snow_making, run_of_the_day, gladed, and moguls. The response also includes total_trails and total_open_trails counts for quick summary displays. All filtering is client-side — no query parameters are accepted, and the full trail list is returned on every call.
Snow Report
get_snow_report returns snow depth data across three named areas: main_lodge, mccoy_station, and summit. Each area object exposes base_depth_in and rolling snowfall totals for the past 24, 48, and 72 hours. Top-level fields include season_total_in, snow_base_range_in, a base_conditions string (e.g. "packed powder"), and a narrative_report in HTML format for richer display contexts. The last_update timestamp tells you when Mammoth last published the report.
Weather Conditions and Forecast
get_weather_report covers current conditions at three elevations (base, midmountain, summit), each with temperature_f, skies, wind_direction, wind_speed_mph, and wind gust data. The forecast array contains daily entries with high_f, low_f, skies, conditions, wind, snow_forecast_in, and comments. This makes it straightforward to build day-by-day trip planning widgets or automated snow-alert pipelines without a separate weather data subscription.
The Mammoth Mountain API is a managed, monitored endpoint for mammothmountain.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when mammothmountain.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official mammothmountain.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Display a live trail map overlay with open/closed status and difficulty ratings from
get_trail_status - Send automated push notifications when
total_open_trailscrosses a threshold - Build a grooming report widget using the
groomedandrun_of_the_dayflags - Show a snow depth comparison across main lodge, McCoy Station, and summit elevations
- Power a trip-planning page with multi-day temperature and snow forecast from
get_weather_report - Track season snowfall progression using
season_total_infrom repeatedget_snow_reportcalls - Alert users when
base_conditionsorlast_24h_invalues change significantly
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Mammoth Mountain offer an official developer API?+
What does `get_trail_status` return, and can I filter by difficulty or area?+
trails array. Each trail includes area, difficulty, status, groomed, gladed, moguls, snow_making, and run_of_the_day fields. No server-side filtering parameters are supported; apply filters to the array on the client using those fields.How fresh is the snow report data?+
last_update ISO 8601 timestamp reflecting when Mammoth Mountain last published that data. The API returns whatever the resort has most recently published — it does not guarantee a specific refresh interval, and update frequency can slow outside peak season or during off-hours.Does the API cover lift status or lift wait times?+
Does the snow report include historical snowfall data beyond the current season?+
get_snow_report exposes season_total_in and rolling 24/48/72-hour totals for the current reporting period only. Prior-season comparisons and historical snowfall archives are not returned. You can fork this API on Parse and revise it to store and serve historical snapshots.