Pull driving-range player session and shot-measurement data using the TrackMan Range API.
domain: docs.trackmanrange.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Sign the TrackMan Data API Terms of Service through a TrackMan sales representative before any access is granted
Authenticate via OpenID Connect/OAuth 2.0 to obtain a signed JWT bearer token from the TrackMan Driving Range authorization server
Send the bearer token in the Authorization header of every request (e.g. GET /api/targets against your range's host)
Use the player-session Measurements endpoints to retrieve individual shot data for a session
Distinguish this Range REST API from TrackMan's other surfaces (Cloud GraphQL API, TM4 device WebSocket protocol, Baseball Data API) — they are separate products with separate documentation
Known gotchas
Access requires a signed Data API Terms of Service via sales, not a self-service signup — budget lead time before a launch date
TrackMan exposes multiple non-interchangeable APIs for golf alone; confirm you are reading docs.trackmanrange.com and not a different TrackMan product's reference
Bearer tokens are signed, short-lived JWTs obtained per authorization flow — plan to refresh them rather than hardcoding one
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?