pgatour.com APIpgatour.com ↗
Access PGA Tour leaderboards, player scorecards, shot-by-shot data, FedExCup standings, and tournament schedules via a single REST API.
curl -X GET 'https://api.parse.bot/scraper/3db295ae-5c87-4ff2-ad38-4956e34b1cbc/get_tournament_leaderboard?tournament_id=R2025001' \ -H 'X-API-Key: $PARSE_API_KEY'
Retrieve the full leaderboard for a specific PGA Tour tournament, including player positions, scores, round details, and tournament status.
| Param | Type | Description |
|---|---|---|
| tournament_idrequired | string | Tournament ID in format R[Year][Number] (e.g., R2025001). |
{
"type": "object",
"fields": {
"leaderboard": "object containing tournament leaderboard data including players array, winner info, courses, rounds, and tournament metadata"
},
"sample": {
"data": {
"leaderboard": {
"id": "R2025007",
"winner": {
"id": "52955",
"purse": "$4,000,000",
"lastName": "Åberg",
"firstName": "Ludvig",
"totalScore": "-12"
},
"players": [
{
"id": "52955",
"player": {
"country": "SWE",
"displayName": "Ludvig Åberg"
},
"scoringData": {
"total": "-12",
"position": "1",
"totalStrokes": "276"
}
}
],
"formatType": "STROKE_PLAY",
"tournamentId": "R2025007",
"tournamentStatus": "COMPLETED"
}
},
"status": "success"
}
}About the pgatour.com API
This API exposes 6 endpoints covering PGA Tour tournament data, returning leaderboards with per-player scoring, hole-by-hole scorecards, and stroke-level shot detail including GPS coordinates and video references. Use get_tournament_leaderboard to retrieve full standings for any tournament by its tournament_id, or get_player_shots to access every stroke a player hit across a specific round.
Tournament Data
The get_tournament_leaderboard endpoint accepts a tournament_id in R[Year][Number] format (e.g., R2025001) and returns a leaderboard object containing a players array with positions, round-by-round scores, and tournament status. The get_tournament_details endpoint accepts a comma-separated list of tournament IDs and returns metadata per tournament: tournamentName, courses, weather, displayDate, and current status. Both endpoints work for past and in-progress tournaments.
Player Scorecards and Shot Data
get_player_scorecard takes a numeric player_id (retrievable from leaderboard response data) and a tournament_id, returning a scorecard object with a roundScores array that breaks down each hole for every round the player completed. For deeper analysis, get_player_shots adds a round parameter (1–4) and returns a shots object with a holes array containing stroke-by-stroke entries — each with distance, location codes, geographic coordinates, and video references where available.
Schedule and Standings
get_schedule accepts an optional year parameter (e.g., 2025) and returns a schedule object split into completed and upcoming arrays, each organized by month with tournament names, IDs, and start dates. get_fedexcup_standings requires no parameters and returns the current FedExCup overview including headline text, editorial nodes, and season context — useful for tracking the points race narrative across the season.
- Display a live tournament leaderboard with player positions and round scores during PGA Tour events.
- Build a hole-by-hole scorecard viewer for any player in any completed or in-progress round.
- Map shot trajectories and locations on a course layout using coordinates from
get_player_shots. - Aggregate historical tournament schedules by season year to analyze field composition and event sequencing.
- Link shot video references from the shots endpoint into a highlights or replay interface.
- Track tournament status across multiple events simultaneously using comma-separated IDs in
get_tournament_details. - Monitor FedExCup standings narrative and season context for editorial or fantasy golf applications.
| 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 PGA Tour have an official developer API?+
What does get_player_shots return, and how granular is the data?+
shots object with a holes array covering every stroke in a specified round. Each shot entry includes distance, location codes (e.g., fairway, rough, green), geographic coordinates, and video references. You need a valid player_id, tournament_id, and round number (1–4) to call it.Does the API cover player career statistics or world rankings?+
How do I find a player's numeric ID to use with get_player_scorecard or get_player_shots?+
players array returned by get_tournament_leaderboard. Fetch the leaderboard for any tournament the player appeared in and extract the numeric ID from that response.