GolfCourseAPI

Home

Pricing

Changelog

New fields, new endpoints, and everything else that changes in the GolfCourseAPI.

Releases follow semantic versioning, and we hold a strong policy against breaking changes: we will not ship one, and we will not bump the major version, unless we feel it is absolutely necessary. An integration you write today should keep working. The full reference lives in the API docs.

v1.3.0

October 6, 2026

Added GET /v1/proximity, which finds courses within a radius of a point and returns them nearest first. Each result is the same course summary GET /v1/search returns, plus distance: the great-circle distance from your point, in the unit you asked for, rounded to two decimals. The response also echoes that unit.
latitude (-90 to 90) and longitude (-180 to 180) are required. unit is mi (the default) or km. radius defaults to 10 and is capped at 50 mi or 80 km. limit defaults to 10 and is capped at 25. Values outside these ranges get a 422 that names the field.
Available on the Pro and Enterprise plans; Free accounts get a 403. Each call counts toward your plan's usage like any other request.
Courses we have no coordinates for are never returned, since there is nothing to measure a distance from.
Purely additive: no existing endpoint or field has changed, so nothing you already depend on needs updating.

v1.2.0

September 24, 2026

Added meters to each hole in tees in the response from GET /v1/courses/{id}: the hole's length in meters, alongside the existing yardage.
It is populated for courses whose scorecards are published in meters and omitted everywhere else, so treat it as optional and keep using yardage as the length that is always present.
Purely additive: every existing field keeps its name and its type, so nothing you already depend on has changed.

v1.1.0

September 13, 2026

Added location.latitude and location.longitude to the responses from GET /v1/search and GET /v1/courses/{id}. Both are decimal degrees and read-only.
Coordinates are omitted for the small number of courses we have no coordinates for, so treat both fields as optional.
Purely additive: every existing field keeps its name and its type, so nothing you already depend on has changed.

v1.0.0

Initial release

Course search, course detail, tee box data, course rating and slope rating.

Something not behaving the way this page describes? .