Book a tee time at a golf club using the Lightspeed Golf (Chronogolf) Partner API V2.
domain: partner-api.docs.chronogolf.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Exchange your refresh token for a 2-hour access token via POST /oauth/token (grant_type=refresh_token) against the production or staging Chronogolf host, and store the newly issued refresh token since the old one is invalidated
Call GET /partner_api/v2/organizations to find the club (organization) UUID your integrator is connected to
Read the tee sheet with GET /partner_api/v2/organizations/{org}/teetimes filtered by filter[date] and filter[course], adding custom_params[player_types][] and custom_params[with_pricing]=true for priced slots
Create a reservation_request against the chosen teetime UUID, then confirm it into a reservation — booking is a 3-step flow, not one call
Inspect the resulting reservation's rounds array, checking each round's cart_fee/kit_fee/green_fee fields to confirm what was actually booked and charged
Known gotchas
V1 (integer ids, flat JSON) and V2 (UUIDs, JSON:API) are not interchangeable — a V1 id 404s on a V2 endpoint and vice versa; new integrations must use V2
There is no self-service developer portal — credentials are provisioned by emailing golf.api@lightspeedhq.com, and staging/production credentials are separate
A newly connected club can take up to 5 minutes to appear in GET /organizations because the connection list is cached
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?