About

The golf leaderboard API is designed to be as simple as possible to get your application up and running as fast as possible.
#Structure
To help speed things up, each endpoint returns two objects, a meta object and a results object. The meta object is really just for developers to get an idea of what they’re seeing in the results object. It includes definitions of the various fields found in the results object and serves as documentation.
#Tours Endpoint
The tours endpoint should be the starting point of your application. It is relatively static, only updating about once a year and detailing season availability. Current tournaments are denoted using the active attribute.
#Fixtures Endpoint
The fixtures endpoint is used to list all competitions within a certain tour and is updated regularly. Due to Covid we added a status variable to determine whether a tournament is cancelled or scheduled. Do not use this variable to determine if a competition is complete, that is catered for in the Leaderboard endpoint. There are some tournaments which overlap tours such as Majors. In this case we endeavour to not list duplicates and list the competition in one tour. Take note of the timezone attribute for each tournament to cater for the tee_time values in the Leaderboard enpoint
#Leaderboard Endpoint
The leaderboard is updated constantly for each competition from the moment that tee times are available - this is usually the day before play is scheduled to start.

Live Details

Pay attention to the live_details object, it has all the information on the current status of the tournament.

Leaderboard

The leaderboard is structured to include everything needed to display a rich leaderboard in your application, the players overall position in the current competition as well as containing an array of rounds they’ve competed in. Player strokes are only updated at the completion of each round.

World Rankings

The world rankings endpoint is useful for clients looking to display info on on the owgr classification system