Cycling Overview

Introduction

The Cycling API provides schedules and results for top competitions. Data is collected via Sportradar operators and is available post-event. Select the Cycling package in our Coverage Matrix for competitions and data offered.

This API uses a descending, stage-based structure. By changing the stage ID, you can retrieve information on a sport, season, discipline, or event.

Additional feeds provide a host of complementary stats, including:

Rankings
Team and competitor profiles
Historical results

🗝️
Authentication is required for all API calls.

Stage Format

The Cycling API uses generic stage implementation. The core of the API is built around the concept of stages. Each stage type (season, discipline, event, stage) will include sub-stages, usable in the same URL path to request information about that particular stage.

See the below Stage Types table for all available stage types, their sub-stages, and their definitions.

The best way to start the navigation with the Cycling API is using the Seasons endpoint. From there, obtain the stage ID for the season required and use that in the Stage Summary as a starting point into the sub-stages.

Stage Types

Stage Type	Information Included	Sub-stages
Sport `sport` `sr:stage:26821`	Information about the seasons included	Cycling seasons
Season `season`	Contains the season schedule for men's or women's cycling	Disciplines on the Cycling calendar for that season (eg. UCI World Tour)
Discipline `discipline`	Scheduling information for all events within a given discipline	Events (eg. Tour de France)
Event `event`	Information about a single event, the stages, the competitors, the teams, and the results	Stages within an event (eg. Stage 1, Stage 2, etc.)
Stage `stage`	Competitors and results of a stage	None

API Map

To best utilize the Cycling API, you will need several parameters to create your API calls. The map below illustrates how you can obtain the parameters you need.

The primary feeds require only a human-readable parameter to call the endpoints. Those feeds provide Stage Ids and Competitor Ids which can be used to generate the profile, summary, and schedule feeds.

Endpoint Descriptions

Competitor Merge Mappings - Provides the valid Sportradar Id in cases when two competitors have been merged into one.

Competitor Profile - Returns biographical information for a given competitor.

Rankings - Returns competitor rankings for the current week.

Seasons – Returns a list of available seasons.

Stage Schedule - Returns a schedule for a given stage.

Stage Summary - Provides schedules and results information based on the stage provided (sport, season, discipline, event, or stage).

Data Retrieval Sample

To find the results for a given race:

Call the Seasons resource for a list of seasons, making note of the Stage Id for your desired season
Call the Season Schedule using the Stage Id and locate your desired race
Call the Sport Event Summary using your race Stage Id

The summary for your race is displayed.

Integration Resources

OpenAPI Spec

Our Cycling API is available via OpenAPI. Click below to view and/or download the specs.

Cycling v2 OpenAPI

Postman Workspace

🚀
Run in Postman
Our full Media API suite—including the Cycling collection—lives in our public Postman workspace. Fork or follow any collection to get updates automatically.

Schema Download

Open the zip file below to access our entire Cycling API XSD schema.

Cycling v2 Schema

MCP Server

The Sportradar Cycling MCP Server is a Model Context Protocol (MCP) implementation that bridges AI assistants directly to our Cycling API feeds. It allows LLMs to use standardized tools to fetch our sports data, helping to power your applications, assist in coding, and streamlining your integration.

For detailed instructions on how to set up and use this integration, visit our MCP Server documentation.