World Snowboard Tour APIworldsnowboardtour.com ↗
Access WSPL rankings, rider profiles, event schedules, and competition results across 6 snowboard disciplines via the World Snowboard Tour API.
What is the World Snowboard Tour API?
This API exposes 8 endpoints covering the World Snowboarding Points List (WSPL), rider profiles, event schedules, and competition results across six disciplines — Big Air, Halfpipe, Slopestyle, Freeride, Rails, and Knuckle Huck. The get_points_list endpoint returns paginated ranked athletes with discipline-specific points and event stop scores, while get_event_results delivers per-athlete scores, finishing positions, and ranking points for any individual competition stop.
curl -X GET 'https://api.parse.bot/scraper/12dbebfe-cbec-4aa9-bedb-9c4e3c01eacc/get_points_list?page=1&gender=1&discipline=3' \ -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 worldsnowboardtour-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.
from parse_apis.world_snowboarding_api import WorldSnowboarding, Discipline, Gender
client = WorldSnowboarding()
# Browse top slopestyle rankings for men
for rider in client.rankedriders.list(discipline=Discipline.SLOPESTYLE, gender=Gender.MEN):
print(rider.rank, rider.first_name, rider.last_name, rider.country.ioc, rider.sum_points)
# Navigate from a ranked rider to their full profile
top_rider = next(iter(client.rankedriders.list(discipline=Discipline.BIG_AIR, gender=Gender.WOMEN)))
profile = top_rider.details()
print(profile.first_name, profile.last_name, profile.athlete_gender)
print(profile.career_stats.competition_wins, profile.career_stats.avg_finish_position)
# Browse upcoming events filtered by country
for event_summary in client.eventsummaries.list(nation="CAN"):
print(event_summary.name, event_summary.city, event_summary.date_from, event_summary.status)
# Drill into event details and get competition results
event = next(iter(client.eventsummaries.list(discipline=Discipline.SLOPESTYLE))).details()
for comp in event.competitions:
print(comp.name, comp.date)
for result in event.results.list(competition_id=event.competitions[0].id):
print(result.athlete, result.end_position, result.score, result.ranking_pts)
# Get discipline rankings for both genders at once
ranking = client.disciplinerankings.get(discipline=Discipline.HALFPIPE)
for r in ranking.men:
print(r.rank, r.first_name, r.last_name, r.country.name)
# List news articles
for article in client.articles.list():
print(article.title, article.date, article.link)
Retrieve the World Snowboarding Points List (WSPL) rankings. Returns paginated ranked athletes for a given discipline and gender. Each result includes rank, total points, and per-event score breakdowns. Paginates via integer page counter.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination. |
| gender | integer | Gender filter. |
| discipline | integer | Discipline filter. |
{
"type": "object",
"fields": {
"next": "string or null, URL of next page",
"current": "integer, current page number",
"results": "array of ranked athlete objects with id, rank, first_name, last_name, country, sum_points, event_stops_scores"
},
"sample": {
"data": {
"next": "https://wyldata.com/api/iframes/wspl-ranking/8/?discipline=5&format=json&gender=1&page=2",
"current": 1,
"results": [
{
"id": 33023,
"rank": 1,
"country": {
"id": 80,
"ioc": "CAN",
"name": "Canada"
},
"last_name": "Brearley",
"first_name": "Liam",
"sum_points": "926.09",
"event_stops_scores": {
"others": [],
"counted": {}
}
}
]
},
"status": "success"
}
}About the World Snowboard Tour API
Rankings and Rider Data
The get_points_list endpoint returns the official WSPL standings, filterable by gender (1 for Men, 2 for Women) and discipline ID. Each ranked entry includes id, rank, country, sum_points, and an event_stops_scores array that breaks down points per stop. The get_rankings_by_discipline endpoint offers a shortcut for side-by-side Men/Women leaderboards with a configurable limit on how many top riders to return.
Rider detail is available through get_rider_profile, which accepts a rider_id sourced from either get_points_list or get_riders_list. The profile includes a career_stats object with fields for competition_starts, competition_wins, competition_podiums, avg_finish_position, and best_run_score, plus a recent_results array. get_riders_list paginates all registered athletes and includes each rider's disciplines array and athlete_gender.
Events and Competition Results
get_events_schedule retrieves the global event calendar with filters for nation (ISO country code such as USA, JPN, AUT), date_from, date_to, and discipline. Results are ordered by date descending and include event-level fields like city, status, competitions, and disciplines. Drilling into a specific event with get_event_details returns individual competition objects — each with its own id, discipline, gender, and date — that feed directly into get_event_results.
get_event_results accepts a competition_id from get_event_details and returns each athlete's score, end_position, ranking_pts, and country. The get_news_list endpoint surfaces up to 10 recent WordPress post objects from worldsnowboardtour.com, including title, content, link, date, and categories.
The World Snowboard Tour API is a managed, monitored endpoint for worldsnowboardtour.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when worldsnowboardtour.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 worldsnowboardtour.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?+
- Build a live WSPL leaderboard app filtered by discipline and gender using
get_points_list - Track a specific athlete's career podiums, win rate, and recent results via
get_rider_profile - Aggregate per-stop scores across a season to chart ranking progression over time
- Display an upcoming event calendar filtered by country and discipline for a regional snowboard fan site
- Compare top Men and Women rankings side by side for a given discipline using
get_rankings_by_discipline - Retrieve detailed competition results including scores and positions for post-event reporting
- Power a news feed widget showing the latest World Snowboarding announcements via
get_news_list
| 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 World Snowboarding (worldsnowboardtour.com) have an official public developer API?+
What does `get_event_results` return and how is it different from `get_events_schedule`?+
get_events_schedule lists events with metadata such as name, city, status, and disciplines — it does not include per-athlete results. get_event_results accepts a competition_id (retrieved from get_event_details) and returns result-level data: each rider's score, end_position, ranking_pts, and country.Can I retrieve athlete photos, social media links, or biographical data through the rider endpoints?+
get_rider_profile covers career statistics (competition_wins, competition_podiums, avg_finish_position, best_run_score) and recent results, but does not include photos, social handles, or biographical text. You can fork this API on Parse and revise it to add an endpoint targeting that additional profile data.Does `get_news_list` support filtering by category or date, or return more than 10 articles?+
What discipline IDs are supported across the filtering endpoints?+
get_points_list, get_events_schedule, and get_rankings_by_discipline.