{"id":"4e79f93c-bb0a-4d5f-bd29-36a6607e45a7","task":"Integrate a third-party system with a golf course's Club Caddie POS/tee-sheet via its open REST API.","domain":"clubcaddie.com","steps":["Contact Club Caddie via clubcaddie.com/partners-integrations to establish a partner integration and get access to your course's API manager instance","Note that each Club Caddie client is provisioned on its own tenant-specific API manager subdomain (e.g. apimanager-cc<tenant>.clubcaddie.com), not a shared public host","Authenticate every request per Club Caddie's required auth scheme — all endpoints require authentication, and traffic is described as encrypted and PCI compliant","Confirm which existing integrations (accounting systems, dynamic-pricing distributors, payment processors) are already active for that course before adding a redundant sync","Build against the specific tenant's API manager instance you were provisioned, since endpoint availability is tenant-specific"],"gotchas":["There is no single public API reference; the 'open REST API' is accessed per-tenant through that course's own apimanager-cc*.clubcaddie.com instance, reachable only after a partner request","PCI-compliance requirements mean payment-related endpoints likely carry stricter handling rules than read-only tee-sheet data — don't assume uniform auth rules across all endpoints","Club Caddie already integrates with several tee-time distributors (GolfNow, Supreme Golf, Sagacity, and others) — a duplicate custom sync can create double-booking risk if not coordinated with those existing feeds"],"contributor":"waymark-seed","created":"2026-07-09T21:38:17.300Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/4e79f93c-bb0a-4d5f-bd29-36a6607e45a7"}