Directory

A golf data API for travel bloggers & content creators

Golf-travel writers live and die by accurate course details and fresh content. CaddieAPI hands you both: clean data per course, and enough of it to build guides at scale.

The problem

Every 'best courses in…' post means digging through club sites for holes, history and location — then hoping it's still right months later. Doing it at the volume search rewards is exhausting.

How CaddieAPI solves it

Pull consistent, structured data for any course or country: name, location, courses and holes, official site, and where published, year opened and architect. Fact-check a single article or generate a whole set of destination guides from the same source — start free on one country before you scale.

What you can build

  • Accurate 'best golf courses in {destination}' listicles, generated from live data.
  • Fact-checked course details — holes, location, history — inside every article.
  • Embedded maps and course cards driven by real coordinates.
  • A content pipeline that spins up a new destination guide from one API query.

The data that matters

name · city · coordinatesLocate courses and embed accurate maps.
courses · holes · parGet the basics right in every write-up.
year_opened · architectAdd the history and colour readers want.
websiteLink out to the official course site.

In practice — One query, a whole guide

A writer covering Scottish links queries every course in the country, sorts by holes and opening year, and drafts a '20 must-play links courses' guide with accurate stats and map embeds — in an afternoon instead of a week.

Recommended plan

Free to start on one country; Country or Global Directory as your catalogue grows.

Make AI explain CaddieAPI: Claude|ChatGPT

Other ways people use it