Yahoo Sports Golf Leaderboard API

Endpoint facts

Method

GET

API path

/yahoo-sports/golf-leaderboard

Auth

apiKey

Credits

2 credits/request

Platform

Yahoo Sports

Response schema

#/definitions/yahoosports.golfLeaderboardResponseDoc

Overview

Returns one golf tournament's full leaderboard (every golfer's rank, to-par score, status, holes-completed-in-current-round, per-round strokes, and a fixed stat set: earnings, eagles, birdies, pars, bogeys, double bogeys), from Yahoo Sports' own public tournament-leaderboard JSON API. Get the `tournament` id from a golf-schedule response's `id` field, e.g. `golf.e.23`. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

2 credits/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Response behavior

- `entries` preserves Yahoo's own leaderboard ordering (by rank). - `rank` is a string and may carry a tie prefix, e.g. `T1`. - `score`/`score_display` are relative to par for the whole tournament (e.g. `-22`, `E`, `+3`); each entry in `rounds` carries the same pair for that round alone. - `status` is one of `IN_PROGRESS`, `FINISHED`, `MISSED_CUT`, `WITHDRAWN`, or `DISQUALIFIED`. A golfer keeps a real `rank`/`score` even after missing the cut, withdrawing, or being disqualified — these are not blanked out. - `thru` is the golfer's holes-completed count for the tournament's current round specifically (`tournament.current_round`), not simply their furthest-along round — a golfer who has already finished today's round still reports that round's holes-completed (typically 18) rather than 0 from tomorrow's not-yet-started round. - `rounds` is round-level only (strokes and to-par score per round); full hole-by-hole shot detail is not included, matching this platform's existing game-boxscore-stops-at-team-totals convention. - `stats` is a fixed set (earnings, eagles, birdies, pars, bogeys, double bogeys) matching what Yahoo's own tournament page requests by default; a zero-valued stat is omitted. - Invalid `tournament` values return an invalid-parameter error before upstream IO; an unknown tournament id returns a 404. Example response: ```json { "code": 200, "msg": "OK", "data": { "tour": "pga-tour", "season": 2026, "tournament": { "id": "golf.e.17", "name": "Wyndham Championship", "status": "FINAL", "start_date": "2026-08-06-07:00", "end_date": "2026-08-09-07:00", "current_round": 4, "rounds": 4, "purse": "8500000.00", "venue": { "name": "Sedgefield Country Club", "city": "Greensboro", "state": "North Carolina", "country": "United States" }, "url": "https://sports.yahoo.com/golf/pga-tour/2026/wyndham-championship/" }, "count": 147, "source_url": "https://graphite.sports.yahoo.com/v1/query/shangrila/playbookGolfTournament?...", "fetched_at": "2026-08-14T07:05:00Z", "entries": [ { "rank": "1", "player": { "id": "golf.p.24201", "name": "Michael Brennan", "short_name": "M. Brennan", "country": "United States", "url": "https://sports.yahoo.com/golf/players/Michael+Brennan/24201/" }, "score": -22, "score_display": "-22", "status": "FINISHED", "thru": 18, "rounds": [ { "round": 1, "strokes": 66, "score": -4, "score_display": "-4" }, { "round": 2, "strokes": 65, "score": -5, "score_display": "-5" }, { "round": 3, "strokes": 63, "score": -7, "score_display": "-7" }, { "round": 4, "strokes": 64, "score": -6, "score_display": "-6" } ], "stats": { "earnings": "$1530000.00", "eagles": 1, "birdies": 25, "pars": 42, "bogeys": 3, "double_bogeys": 1 } } ] } } ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related