Authenticate and read a golf club's tee-sheet resources using the Golfmanager API.
domain: github.com/golfmanager/api_v1 · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Generate an admin ApiKey and a consumer ApiKey pair from the ApiKeys page, or request them from the Golfmanager team for your tenant
If working against a local/self-hosted superadmin instance, add your host/tenant on the Hosts page before making any calls
Authenticate with HTTP Basic Auth using the username/password returned when the ApiKey was generated
Call GET /tenants and GET /tenant to confirm which tenant context you are scoped to
Read GET /resources (bookable resources such as bays and courses) and GET /reservationtypes to understand what can be booked before calling /searchAvailability
Known gotchas
The /tenants endpoint and its routing logic live in a different source file than the rest of the documented endpoints — don't assume every endpoint follows the same code path if you're also reading the source
Admin vs. consumer privilege filters are per-endpoint (admin by default unless the endpoint explicitly says otherwise) — using the wrong key type returns an authorization error, not empty data
There is no universal public sandbox; each integrator works against their own tenant's ApiKey pair
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?