Skip to main content

Build with golf data

The E.A.E Golf API provides normalized golf club and course information for applications and AI agents, with REST and native MCP access.

Golf clubs publish their information in many different formats and languages. Names, access conditions, course details, green fees and amenities may be presented differently from one club to another.

The API converts this information into one predictable, machine-readable data structure. Applications can work with consistent fields and canonical values instead of implementing separate parsing logic for every club or country.

Available data​

Depending on the information published by each club, API records can include:

  • Club names and contact details
  • Postal addresses and geographic coordinates
  • Courses and number of holes
  • Public access
  • Membership and handicap requirements
  • Access for independent players without club membership
  • Green fees and currencies
  • Available facilities and amenities
  • Golf lessons and practice facilities
  • Equipment rental
  • Dog and leash rules
  • Terrain and course characteristics

Not every club publishes every type of information. Fields whose values cannot be reliably determined may be returned as null or omitted, depending on the endpoint and response schema.

For the complete structure, see the data model. For language-neutral values and localized presentation text, see Localization.

Applications can search for clubs using geographic coordinates and a radius:

GET /v1/clubs?near=Hamburg&country=DE&radius_km=50

Field-specific filters are also available for values such as town, postal code, public access and other club characteristics.

Consult the API reference for the complete list of supported parameters.

Authentication​

Protected endpoints require an API key. Send the key as a Bearer token in the Authorization header:

Authorization: Bearer YOUR_API_KEY

API keys can have different permissions, rate limits and application restrictions.

Start here​

  1. Choose a Fairway or Tour trial.
  2. Register your application and request an API key.
  3. Store the key securely.
  4. Follow the agent quickstart, connect through MCP, or make a REST request.
  5. Use the API reference for supported endpoints and parameters.

API stability​

Endpoints are versioned through the URL:

/v1

Versioned endpoints provide a stable contract for integrations. New optional fields may be added without changing the API version, while incompatible structural changes will be introduced under a new version.