Skip to main content

Get one golf club

Retrieve the detailed record for one golf club using its UUID or slug:

GET /v1/clubs/{identifier}

Use the club UUID as the recommended stable identifier for integrations. The existing unique slug remains supported for readable URLs and backwards compatibility.

Example request​

curl 'https://api.eae.golf/v1/clubs/b6bcc5e7-6c80-459e-98f8-afe5e2594ae2' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Accept: application/json'
curl 'https://api.eae.golf/v1/clubs/golf-gut-glinde' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Accept: application/json'

Obtain an identifier​

Club list and search responses include both identifiers:

{
  "id": "b6bcc5e7-6c80-459e-98f8-afe5e2594ae2",
  "slug": "golf-gut-glinde",
  "name": "Golf Gut Glinde"
}

Applications should store the returned UUID for integrations. Do not generate a slug from a club name: punctuation, legal suffixes and duplicate names can make client-generated identifiers unreliable.

Successful response​

A successful request returns 200 OK and the club's detailed public record. Depending on the available data, the response can contain contact information, geographic coordinates, courses, access conditions, amenities, etiquette and green fees.

Some fields may be null when the value cannot be established reliably. A missing or unknown value must not automatically be interpreted as false.

Club not found​

An unknown UUID or slug returns:

404 Not Found

Check that the UUID or slug was copied exactly from an API response. Club names are not accepted in place of the path identifier. Use the clubs endpoint with name or search when only a name is known.

curl 'https://api.eae.golf/v1/clubs?name=Green%20Eagle&limit=20' \
  --header 'Authorization: Bearer YOUR_API_KEY'

Cache club details​

Club records generally change less frequently than search results. Follow the response's cache headers and use conditional requests when supported. Do not assume a club record remains unchanged indefinitely.