domain: dev.sportsengine.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register an OAuth2 application in the SportsEngine developer portal to get client credentials
Select the right OAuth2 flow for the use case: PKCE for user-facing apps, Client Credentials for server-to-server jobs
For SSO, integrate OpenID Connect separately to authenticate users and establish identity in your own system
Use the GraphQL Explorer/schema docs to build queries for organizations, teams, rosters, and schedules
Have the target organization complete SportsEngine's authorization workflow to grant your app data-access permission
Consult the separate Commerce API docs if payment/order data is also needed
Known gotchas
Organizations must explicitly authorize your app before it can read their data - there is no blanket account-level access
SportsEngine has both a legacy v1 REST API and a newer GraphQL API; documentation is split across multiple portals
SSO (OIDC) and the GraphQL data API are separate integrations that are easy to conflate during planning
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?