Overview

This guide explains how to build with the Sportradar Formula 1 API: the stage-based model behind the data, the basics of making requests, and step-by-step integration scenarios. It complements the API reference, which documents each endpoint field by field.

---

Who This Is For

These guides are for developers integrating Formula 1 data into an application: live timing screens, race and championship pages, fantasy and prediction products, broadcast graphics, and research tools. They assume general REST API experience but no prior experience with Formula 1 data; the Fundamentals guide covers the stage-based vocabulary you need.

---

Prerequisites

• A Sportradar account and a Formula 1 API key (trial or production). See API Basics for authentication and base URLs.
• Familiarity with HTTP and either JSON or XML; every feed supports both formats.

---

Guides vs the API Reference

The two are complementary:

• The Integration Guides (these pages) explain how and why: the stage model, the status lifecycle, polling strategy, and worked examples.
• The API Reference documents what: every endpoint, parameter, and response field.

When a guide mentions a feed, it links to that feed's reference page rather than duplicating the field dictionary.

---

What the Formula 1 API Covers

The Formula 1 API provides schedules and live, lap-by-lap coverage for the entire Formula 1 World Championship, plus the supporting data developers build around it:

• Driver and constructor (team) championship standings
• Race, event, and championship win probabilities
• Driver (competitor) and team profiles
• Circuit and venue information
• Commentary and key terms translated into multiple languages

For the current package-level breakdown of events and data points, select the Formula 1 package in the Coverage Matrix.

A few scope notes:

• The API is a standalone, stage-based product. It shares the stage-based model with Sportradar's other motorsport APIs (IndyCar, MotoGP, Formula E, Rally, Indy Lights); the league-based NASCAR API uses a different model. See Fundamentals.
• The API is poll-based: live data is retrieved by polling the REST feeds. See Update Frequencies.
• Trial keys serve historical and replay data. Production keys cover the season live. See Historical Data.

---

How the Guides Are Organized

The map below shows the four tiers and every page in each; each pill links to its guide.

Each scenario is described in the where-to-start table on the Integration Scenarios landing page, and the Race Status Workflow page is the canonical status reference the other guides lean on.

---

Recommended Reading Order

New to the Formula 1 API: read API Basics, then Fundamentals, then the Integration Scenarios landing page, and finish with the scenario that matches your use case.

Experienced with Sportradar APIs: skim API Basics for the F1-specific URL shapes, read Fundamentals and the Race Status Workflow page (the stage model differs from the league-based APIs), then go straight to your scenario.

---

Companion Tools

• Postman: a Sportradar Formula 1 workspace to exercise the feeds without code.
• OpenAPI spec: the Formula 1 v2 OpenAPI spec describes every endpoint, parameter, and enum.
• Schema download: XSDs for validating xml responses.
• MCP Server: the Sportradar Formula 1 MCP Server connects AI assistants to the feeds.

See API Basics for details on each.