Tour de France Stage & Classification Tables

Tour de France Stage & Classification Tables returns structured Tour de France stage results and classification tables by edition year and stage. Use it to collect stage standings, overall standings after a selected stage, points, mountains, young rider, and team classifications without managing race-page URLs yourself.

The actor is focused on one competition, so the input stays small: choose a year, choose one stage or all stages, select the tables you need, and set the maximum rank. Output rows are normalized for dashboards, fantasy cycling tools, editorial databases, betting models, sports archives, and API workflows.

Why Use This Actor

• Get Tour de France data without selecting from a generic cycling race list.
• Pull one stage or every stage in the edition.
• Return stage-by-stage classification snapshots, not only final standings.
• Inspect separate Apify output datasets for stage results, overall, points, mountains, young rider, and team tables.
• Export clean rows by year, stage, classification, rank, rider, team, time, gap, and points.
• Append rows to an existing Apify dataset with datasetId when using a larger pipeline.

What It Produces

The actor can return these table types:

• stage result
• overall / general classification after the selected stage
• points classification after the selected stage
• mountains classification after the selected stage
• young rider classification after the selected stage
• team classification after the selected stage

All rows are written to the default dataset. The actor also writes each table type to its own run-scoped output dataset, so Console users can open Stage Results, Overall / GC, Points, Mountains, Young Rider, or Team without seeing unrelated rows.

Use Cases

• Fantasy cycling platforms importing leaders and top riders after each stage.
• Sports journalists checking the classification picture on a specific day.
• Cycling analysts building stage-by-stage Grand Tour history tables.
• Betting and prediction tools comparing race position changes.
• Fans or archivists maintaining structured Tour de France dashboards.

How To Use

1. Enter the edition year, for example 2024.
2. Set Stage to all or a stage number such as 12.
3. Choose the classifications to return.
4. Set Max Rank.
5. Run the actor and download JSON, CSV, Excel, or consume the dataset through the API.

Input Example

{
  "year": 2024,
  "stage": "12",
  "classifications": ["stage", "general", "points", "mountains", "young", "team"],
  "maxRank": 10
}

Input Reference

Field	Type	Description
year	integer	Four-digit Tour de France edition year.
stage	string	Use all for every discovered stage or a stage number such as 12.
classifications	array	One or more of stage, general, points, mountains, young, team.
maxRank	integer	Highest rank returned per selected table.
datasetId	string	Optional existing Apify dataset ID to append rows to.
runId	string	Optional workflow identifier copied into output rows.
proxyConfiguration	object	Apify proxy settings. Residential proxy is the default because the public race pages often block cloud datacenter traffic.

Output Example

{
  "raceName": "Tour de France",
  "editionYear": 2024,
  "stageNumber": 12,
  "stageName": "Aurillac > Villeneuve-sur-Lot",
  "classificationType": "general",
  "rank": 1,
  "riderName": "Tadej Pogacar",
  "riderNationality": "Slovenia",
  "teamName": "UAE Team Emirates",
  "time": "49:17:49",
  "winner": true
}

Output Reference

Field	Description
raceName	Race name.
editionYear	Race edition year.
stageNumber	Stage number represented by the row.
stageName	Stage route or label when available.
stageDate	Stage date when available.
classificationType	stage, general, points, mountains, young, or team.
rank	Position in the table.
riderName	Rider name for rider-level rows.
riderNationality	Rider nationality when available.
teamName	Rider team or team classification entry.
time	Recorded time when available.
timeBehind	Gap to the winner or leader when available.
points	Points total when available.
winner	true when rank is 1.
runId	Optional workflow ID supplied in the input.

API Example

curl "https://api.apify.com/v2/acts/TroveVault~tour-de-france-stage-classification-tables/runs?waitForFinish=120" \
  -X POST \
  -H "Authorization: Bearer YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "year": 2024,
    "stage": "12",
    "classifications": ["stage", "general", "points"],
    "maxRank": 10
  }'

Limitations

Coverage is strongest for modern editions with complete public race records. Older editions can have fewer stage details or missing secondary classifications. Some stages may not have every classification table, especially if a classification was not active or the public record is incomplete for that edition.

The actor returns normalized cycling rows, not diagnostic source-navigation data. If a table is not found, the run still completes and records missing table details in RUN_SUMMARY.

FAQ

Can I search one stage?

Yes. Set stage to a number such as 12.

Can I get every stage?

Yes. Set stage to all. The actor discovers stage pages for the selected edition and returns the selected classifications for each stage.

Are final standings included?

For Grand Tours, the last stage classification snapshot represents the final race state. Use stage: "all" to collect every stage snapshot, including the final stage.

Are the classifications separate datasets?

Yes. The default dataset contains all rows, and the run output also links to separate datasets for stage results, overall, points, mountains, young rider, and team tables.

Can I use this with MCP or scheduled workflows?

Yes. Run it through Apify API, schedules, integrations, or MCP workflows. Use datasetId and runId when you need to append rows or tag downstream exports.

Related Actors

Use this actor when you need a focused Tour de France table. Use the broader Professional Cycling Results & Classifications actor when you need many races from one generic input.

Changelog

• 0.1: Initial TroveVault release with stage results and stage-by-stage classification tables.

Support

Open an issue in the actor discussion tab with the year, stage value, selected classifications, and run ID.