Manage a golf club's member/client CRM records using the Golfmanager API.
domain: eu.golfmanager.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with an admin-scoped API key (HTTP Basic Auth, or the 'key' header plus tenant)
Call GET /clients for a lightweight client list, or GET /clientsFull for the fuller client record set
Create or update a member record with POST /saveClient
Organize members with GET /clientGroups / POST /saveClientGroup, and tag them via GET /clientTags, POST /saveTag, and /saveClientTags (removing with /deleteClientTag)
Paginate large client lists using the limit (1-100) parameter and the lastId cursor, checking hasMore in the response before requesting another page
Known gotchas
/clients and /clientsFull are separate endpoints with different payload weight — defaulting to /clientsFull for a simple lookup list wastes bandwidth on large member rosters
Pagination uses lastId + hasMore rather than page numbers — offset/page-based pagination logic ported from another API will not work here
Tags and client groups are separate object types with separate save/delete endpoints; conflating them saves data to the wrong bucket
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?