Charge and track member dues/billing through a club-management API's membership endpoints.
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 against the club-management system (e.g. Golfmanager)
Call GET /membership to list the club's defined membership/dues products, and POST /saveMembership to create or update one
Call GET /membershipClient to see which members hold which membership, and POST /saleMembership to sell or renew a membership for a specific client
Reconcile billing with GET /sale, /salelines, and /payments, using POST /confirmSalelines to finalize a dues charge as a completed sale
Use GET /paymentMethods / POST /savePaymentMethod to confirm the member's payment method (house account, card on file, etc.) is correctly attached before charging dues
Known gotchas
Selling/renewing a membership (saleMembership) and defining the membership product/price (saveMembership) are separate calls — updating the product definition does not retroactively re-bill existing members
Dues billing routes through the same generic sale/salelines/payments objects used for pro-shop POS transactions — dues are not a first-class 'subscription' object, so recurring billing logic (schedules, retries) must be built on top
A saved payment method must exist and be attached before confirmSalelines succeeds; running dues against a member with no payment method on file fails per-member rather than failing the whole batch silently
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?