Skip to main content

Get one golf club

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

GET /v1/clubs/{slug}

The slug is the club's stable public identifier within the API.

Example request​

curl 'https://api.eae.golf/v1/clubs/green-eagle-golf-courses' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Accept: application/json'

Obtain the slug​

Club list and search responses include the slug:

{
  "slug": "green-eagle-golf-courses",
  "name": "Green Eagle Golf Courses"
}

Applications should store the slug or returned resource URL rather than generating a slug from the 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 slug returns:

404 Not Found

Check that the slug was copied exactly from an API response. Club names are not accepted in place of the path slug. 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.