Professional Cycling Results & Classifications
Pricing
from $0.85 / 1,000 cyclists
Professional Cycling Results & Classifications
Returns cycling race winners, stage results, GC, points, mountains, youth, and team classifications. Export data, run via API, schedule and monitor runs, or integrate with other tools.
Pricing
from $0.85 / 1,000 cyclists
Rating
0.0
(0)
Developer
Trove Vault
Actor stats
1
Bookmarked
3
Total users
1
Monthly active users
13 days ago
Last modified
Categories
Share
Professional Cycling Results & Classifications returns structured race results from a race name and year. Choose a race, select the edition year, pick the result scope, and get clean rows for winners, general classification, points classification, mountains classification, youth classification, team classification, and stage results.
This actor is built for users who want cycling data as a finished information product. You do not need to collect result links first. The actor resolves the selected race internally, normalizes the data, and returns a consistent dataset that can feed fantasy cycling tools, editorial databases, dashboards, betting models, or personal cycling archives.
Why Use This Actor
- Look up a race by name and year instead of managing result-page URLs.
- Get winners across classifications and stages in one run.
- Export rows that are easy to filter by race, year, result type, classification, stage, rank, rider, and team.
- Use a compact winners-only mode for fast answers or a fuller mode for analytics.
- Append rows to an existing Apify dataset with
datasetIdfor pipeline workflows.
What It Produces
The actor can return:
- race classification winners
- top N general classification rows
- top N points, mountains, youth, and team classification rows when available
- stage winners
- top N stage positions when requested
Output is intentionally clean. Public dataset rows do not include source links, diagnostic warnings, scrape timestamps, or error rows. Operational details are kept in logs and the RUN_SUMMARY key-value store record.
Use Cases
- Fantasy cycling platforms importing race winners and stage results.
- Sports journalists checking winners and top rankings for a race edition.
- Cycling analysts building race history tables.
- Betting and prediction tools comparing rider results by race and stage.
- Fans maintaining personal cycling stats or dashboards.
How To Use
- Choose a race from the Race dropdown.
- Enter the race year, for example
2024. - Choose the result scope.
- Set the maximum rank per classification.
- Run the actor and download the dataset as JSON, CSV, Excel, or through the API.
If a race is not in the dropdown, choose Other race and fill Custom Race Name. Custom races are resolved by name and may be less reliable than curated dropdown races.
Input Example
{"raceName": "Tour de France","year": 2024,"resultScope": "winners_only","maxRankPerClassification": 3,"includeStagePositions": true}
Input Reference
| Field | Type | Description |
|---|---|---|
raceName | string | Race selected from the curated dropdown. |
customRaceName | string | Optional race name used only when raceName is Other race. |
year | integer | Four-digit race edition year. |
resultScope | string | winners_only, classifications, stage_results, or full_race. |
maxRankPerClassification | integer | Highest rank returned per classification or stage. |
includeStagePositions | boolean | Return top stage positions when stage results are requested. |
datasetId | string | Optional existing Apify dataset ID to append results to. |
runId | string | Optional workflow ID copied into each output row. |
Output Example
{"raceName": "Tour de France","raceYear": 2024,"resultScope": "winners_only","resultType": "classification","classificationType": "general","rank": 1,"riderName": "Tadej Pogacar","riderNationality": "Slovenia","teamName": "UAE Team Emirates","time": "83:38:56","winner": true}
Output Reference
| Field | Description |
|---|---|
raceName | Race name selected or resolved for the run. |
raceYear | Race edition year. |
resultScope | Scope selected in the input. |
resultType | classification or stage. |
classificationType | general, points, mountains, youth, teams, or stage. |
stageNumber | Stage number for stage rows. |
stageName | Stage name or route label when available. |
stageDate | Stage date when available. |
rank | Position in the classification or stage. |
riderName | Rider name for rider-level rows. |
riderNationality | Rider nationality when available. |
teamName | Rider team or team classification name. |
time | Recorded time when available. |
timeBehind | Gap to the winner or leader when available. |
points | Classification points when available. |
winner | true when rank is 1. |
runId | Optional input run ID copied to output rows. |
API Example
curl "https://api.apify.com/v2/acts/TroveVault~professional-cycling-results-classifications/runs?waitForFinish=120" \-X POST \-H "Authorization: Bearer YOUR_APIFY_TOKEN" \-H "Content-Type: application/json" \-d '{"raceName": "Paris-Roubaix","year": 2024,"resultScope": "winners_only","maxRankPerClassification": 1}'
Limitations
Coverage is strongest for modern professional road races and major events in the curated dropdown. Some older editions, smaller races, discontinued races, or classifications that did not exist for a specific race may return fewer rows. Team, youth, mountains, or points classifications are returned only when the race edition has them available.
The actor is designed to return a clean information dataset. If a race cannot be resolved or no rows are found, check the run log and RUN_SUMMARY for operational details.
FAQ
Do I need result-page URLs?
No. Choose a race and year. The actor handles lookup internally.
Can I get only winners?
Yes. Use winners_only to return classification winners and stage winners.
Can I get top 10 classifications?
Yes. Use classifications or full_race and set maxRankPerClassification to 10.
Can I get stage positions?
Yes. Use stage_results or full_race. Keep includeStagePositions enabled.
Why are some classifications missing?
Not every race has every classification. One-day races usually do not have GC, points, mountains, youth, or team classifications.
Why is the output missing source links?
The actor returns normalized cycling information, not source-navigation data. This keeps the dataset clean for downstream products.
What happens if no rows are found?
The run finishes successfully with an empty dataset and records lookup details in RUN_SUMMARY.
Troubleshooting
- Try a major race from the dropdown first, such as Tour de France or Paris-Roubaix.
- Check the year is correct and uses four digits.
- Reduce
maxRankPerClassificationfor quick tests. - Enable Apify Proxy if the run log shows access or network blocks.
- Use
Other raceonly when the race is not available in the dropdown.
Related Actors
Use this actor alongside sports analytics, news-monitoring, and dataset-enrichment actors when building cycling dashboards or editorial workflows.
Changelog
0.1: Initial TroveVault release with race dropdown, year-based lookup, classifications, stage results, and clean public output.
Support
Open an issue in the actor discussion tab with the race name, year, selected scope, and run ID.