motorsport.com APImotorsport.com ↗
Access F1 news, driver profiles, race schedules, championship standings, and detailed race results from Motorsport.com via 7 structured endpoints.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/dfd791fa-ae96-44c2-8a31-a1db0d09d737/get_f1_news' \ -H 'X-API-Key: $PARSE_API_KEY'
Fetch the latest F1 news headlines from the Motorsport.com RSS feed. Returns a list of recent articles with titles, links, publication dates, and descriptions.
No input parameters required.
{
"type": "object",
"fields": {
"data": "array of news article objects with title, link, pub_date, and description",
"status": "string indicating success"
},
"sample": {
"data": [
{
"link": "https://www.motorsport.com/f1/news/how-competitive-is-the-red-bull-ford-f1-engine-compared-to-mercedes/10820631/",
"title": "How competitive is the Red Bull Ford F1 engine compared to Mercedes?",
"pub_date": "Thu, 14 May 2026 11:23:53 +0000",
"description": "While the opening race weekends of the year proved particularly challenging..."
}
],
"status": "success"
}
}About the motorsport.com API
This API exposes 7 endpoints covering Formula 1 data sourced from Motorsport.com, including current driver profiles, season schedules, championship standings, and per-race results. The get_race_results endpoint returns finishing positions, lap counts, intervals, and points scored for any race identified by its event slug. Combined with get_f1_standings, it gives developers a full picture of a championship season without building their own data pipeline.
News and Headlines
Two endpoints cover F1 news from Motorsport.com. get_f1_news returns a list of article objects with title, link, pub_date, and description fields pulled from the site's RSS feed, making it suitable for applications that need metadata-rich articles. get_latest_news returns a lighter payload — just title and url — sourced from the Motorsport.com news page. If you need publication dates and article summaries, use get_f1_news. If you only need headlines and links, get_latest_news is sufficient.
Driver Grid, Schedule, and Standings
get_f1_drivers returns the current season's driver grid as an array of objects with name, team, details, and profile_url. No year parameter is accepted — it always reflects the current grid. get_f1_schedule accepts an optional year parameter (e.g. '2024', '2025') and returns a schedule array of race event objects with dates and session times. get_f1_standings accepts both a type ('Driver' or 'Team') and a year parameter, returning position, name, points, and per-race point breakdowns for every entry in the standings table.
Race Lists and Detailed Results
To query race results, start with get_race_list, which accepts a year and returns an array of races each with a name, slug, and url. Pass the slug value as the event_slug parameter to get_race_results to retrieve the full finishing order for that event. The results array contains driver finish objects with position, driver name, lap count, race time, interval to the car ahead, and championship points scored. The response also includes a report_url pointing to the Motorsport.com race report for that event.
- Build a live F1 championship tracker using
get_f1_standingsfor both driver and constructor points tables by season year. - Populate a race calendar widget with session dates from
get_f1_schedulefor any supported season. - Create a race-by-race results archive by iterating slugs from
get_race_listand fetching each viaget_race_results. - Display driver team affiliations and profile links in a team roster page using
get_f1_drivers. - Aggregate F1 headlines with publication dates for a news feed app using
get_f1_news. - Analyse points-per-race progression across a full season by combining
get_f1_standingsbreakdown fields withget_race_resultsdata. - Trigger alerts when new headlines appear by polling
get_latest_newsand diffing titles against previously stored results.
| 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 | 250 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 Motorsport.com have an official developer API?+
How do I retrieve results for a specific race rather than the full season?+
get_race_results requires an event_slug parameter. Call get_race_list first with the desired year to get the array of races, each of which includes a slug field. Pass that slug as event_slug to get_race_results. For example, a Bahrain GP slug might look like 'bahrain-gp-639919'. The response includes the full finishing order with lap counts, intervals, and points scored.What years of historical data are available for standings and race results?+
year parameter on get_f1_standings, get_race_list, and get_race_results accepts values like '2023', '2024', and '2025'. Coverage of earlier seasons is not guaranteed, and gaps may exist for seasons prior to 2023. Testing with specific year values is the most reliable way to confirm availability for a given season.Does the API cover qualifying results, sprint races, or practice session times?+
get_race_results covers the main race finishing order, including positions, intervals, lap counts, and points. get_f1_schedule includes session timing data but race-weekend sessions like qualifying or sprint results are not returned as separate structured endpoints. You can fork this API on Parse and revise it to add those missing endpoints.Does `get_f1_drivers` return historical driver rosters or only the current grid?+
get_f1_drivers always returns the current driver grid and does not accept a year parameter. Historical rosters from past seasons are not exposed by this endpoint. You can fork this API on Parse and revise it to add a year-filtered driver endpoint if past grid data is needed.