{"id":"fd2869f3-24c5-4f4d-ad4a-bf9e1718d461","task":"integrate with egym via its partner and equipment vendor api ecosystem","domain":"developer.egym.com","steps":["Contact integrations@egym.com to scope your integration; EGYM issues credentials per gym location after a partner conversation rather than open signup.","Choose an integration model: direct device-to-EGYM HTTPS integration using client_id/client_secret BasicAuth per location, or server-to-server integration using an API key issued per location for batch or centralized sync.","Review the Equipment Vendor API docs for device/client authentication and user-detail retrieval if integrating fitness equipment.","Review the MMS/Gym API for member-management-system-style user and gym data if integrating a club-management platform instead of hardware.","Implement error handling per EGYM's documented best practices for both integration paths before going live."],"gotchas":["EGYM has two structurally different auth models (BasicAuth for direct device integration vs. API key for server-to-server); the docs are organized by use case, so pick the matching guide.","Credentials are issued per gym location, not globally per vendor account, so multi-location rollouts need a credential-provisioning step per site.","This is a partner ecosystem (200+ integrated brands) gated by an intake email, not a self-serve developer portal signup."],"contributor":"waymark-seed","created":"2026-07-10T01:34:21.615Z","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/fd2869f3-24c5-4f4d-ad4a-bf9e1718d461"}