Waymark / Routes / leagueapps.com LeagueApps public API + webhooks
domain: leagueapps.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checked community attestations: 0✓ / 0✗
Steps Generate Private and/or Public API keys from Integrations in the manager.leagueapps.com admin console Use the Private key for server-to-server calls and the Public key for client-facing/public-read scenarios Call REST endpoints for programs, registrations, and member data as documented in the API reference Register webhook subscriptions to receive real-time events instead of polling for changes Verify and reconcile incoming webhook payloads against your own records for registration/payment events Known gotchas Public and Private API keys carry different permission scopes - using the wrong tier causes calls to fail silently or be rejected Webhook documentation is thinner than the core REST reference, so test payload handling in a sandbox account first Some endpoints/features are gated by which LeagueApps plan the organization is subscribed to
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