European Tour APIeuropeantour.com ↗
Access DP World Tour tournament schedules, player search, event fields, leaderboards, hole-by-hole scorecards, and per-round stats via the europeantour.com API.
What is the European Tour API?
Eight endpoints expose DP World Tour golf data from europeantour.com, covering everything from season schedules to hole-by-hole scorecards. Use get_scorecard to pull every round's front-nine, back-nine, and per-hole score classification for any player in any event, or call get_round_stats for driving accuracy, greens in regulation, putts, and field-relative rankings per round. Player lookup, event fields, leaderboards, and career event histories are all accessible with numeric IDs that chain cleanly across endpoints.
curl -X GET 'https://api.parse.bot/scraper/152f9562-8e88-44cc-a2f7-0ec3529525c9/get_scorecard?event_id=2026126&player_id=34024' \ -H 'X-API-Key: $PARSE_API_KEY'
Retrieve a player's hole-by-hole scorecard for all rounds in a tournament. Each hole shows the number of strokes and score classification (eagle, birdie, par, bogey). Returns all completed rounds with front-nine/back-nine/total strokes and score-to-par per round.
| Param | Type | Description |
|---|---|---|
| event_idrequired | string | Numeric tournament event identifier (e.g. 2026126 for Genesis Scottish Open 2026). |
| player_idrequired | string | Numeric player identifier on the DP World Tour (e.g. 34024 for Rory McIlroy). |
{
"type": "object",
"fields": {
"rounds": "array of round objects containing hole-by-hole scoring",
"event_id": "integer — tournament event identifier",
"player_id": "integer — player identifier",
"last_updated": "string — ISO 8601 timestamp of last data update"
},
"sample": {
"data": {
"rounds": [
{
"holes": [
{
"penalty": 0,
"strokes": 3,
"hole_number": 1,
"score_class": "ea"
},
{
"penalty": 0,
"strokes": 4,
"hole_number": 2,
"score_class": "pa"
}
],
"strokes_in": 34,
"strokes_out": 31,
"round_number": 1,
"score_to_par": -5,
"course_number": 1,
"total_strokes": 65
}
],
"event_id": 2026126,
"player_id": 34024,
"last_updated": "2026-07-12T16:43:25+00:00"
},
"status": "success"
}
}About the European Tour API
Tournament Discovery and Scheduling
The list_events endpoint returns DP World Tour events whose dates fall within a requested window, filtered by status (completed, in_progress, or scheduled). Each record includes event_id, name, tour, season, venue, location, country_code, and precise ISO start_date/end_date values. The event_id returned here is the key used by every other endpoint. The seasons_checked array in the response tells you exactly which season schedules were read to build the result.
Player Lookup and Event Participation
Before querying player-specific data, use find_player to resolve a partial or full name to a canonical numeric player_id, along with full_name, country_code, date_of_birth, and a profile URL. Once you have a player_id, list_player_events returns every DP World Tour event that player entered within a date window, including position text, per-round strokes, and an explicit completed boolean. get_event_field returns the full entry list for a given event — each entrant carries entry_category, the category description and rank, an above_cut flag, and a participation_status. The scoring_started boolean distinguishes pre-tournament fields from live or completed leaderboard states.
Leaderboards, Scorecards, and Round Statistics
get_event_results provides the strokeplay leaderboard with position, position_desc, is_tie, round-by-round strokes, total score-to-par, and the cut_value. The event_status field normalises to completed | in_progress | scheduled | other; the raw event_status_code (3 for completed, 0 for in progress, 6 for scheduled) is also returned.
For granular scoring, get_scorecard returns each hole's stroke count and score classification (eagle, birdie, par, bogey, etc.) across all completed rounds, with strokes_out, strokes_in, and score_to_par per round. get_round_stats adds the performance layer: driving_accuracy_pct, driving_distance_yards, greens_in_regulation_pct, putts_per_round, scrambles_pct, and strokes_rank within the field for a specific round. get_player_event_stats consolidates both scorecard and statistics feeds into one response, adding total_penalties, rounds_completed, and event-level aggregate stats keyed by metric.
Data Chaining
All endpoints are designed to chain: list_events → get_event_field or get_event_results; find_player → list_player_events → get_scorecard or get_player_event_stats. IDs are consistent integers throughout, so joining data across multiple endpoints requires no translation.
The European Tour API is a managed, monitored endpoint for europeantour.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when europeantour.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official europeantour.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a live DP World Tour leaderboard display using
get_event_resultswithcurrent_roundandevent_statusfields. - Track a specific player's season history by chaining
find_playerandlist_player_eventsto retrieve every event result within a date range. - Analyse driving distance and greens-in-regulation trends across rounds using
get_round_statsfor any player–event combination. - Populate an event preview page with the full entry list, entry categories, and above-cut flags from
get_event_field. - Compute hole-difficulty statistics across a tournament by aggregating per-hole score classifications from
get_scorecardfor all players in the field. - Compare a player's scramble percentage and putt count against field rankings using
strokes_rankandscrambles_pctfromget_round_stats. - Power a historical performance database by ingesting
get_player_event_statsdata including penalties, score-to-par, and per-round hole-class counts.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does europeantour.com have an official public developer API?+
What does `get_event_results` return, and how do I tell whether an event has finished?+
get_event_results returns the full strokeplay leaderboard including each player's position, round-by-round strokes, total score_to_par, and a cut_value. The completed boolean is set to true only when the event is fully finished. The event_status field normalises site codes into completed, in_progress, scheduled, or other; the raw event_status_code (3, 0, or 6) is also included if you need the original value.Does the API cover Challenge Tour or other DP World Tour feeder events?+
What is the difference between `get_scorecard` and `get_player_event_stats`?+
get_scorecard focuses on hole-by-hole detail: each hole's stroke count and score classification (eagle, birdie, par, bogey) with front-nine, back-nine, and round totals. get_player_event_stats consolidates scorecard data with the round statistics feed to add driving, putting, and scrambling metrics, plus total_penalties and rounds_completed at the event level. Use the scorecard for hole-level granularity and get_player_event_stats for a combined performance summary.