TrackMan
TrackMan A/S is a Danish sports-technology company (headquartered in Vedbaek, Denmark) that builds Doppler radar and optically tracked launch monitors, simulator software, and data platforms for golf, baseball, football, and US football. Its hardware lineage includes the TrackMan 4 outdoor/indoor launch monitor, TrackMan iO indoor launch monitor, the V3 stadium ball-tracking system used by every Major League Baseball club, and the portable B1 baseball launch monitor. On the software side TrackMan operates TrackMan Range (a connected driving-range platform), Virtual Golf 3 (the simulator rendering and gameplay engine), the TrackMan Golf App for performance and social play, TrackMan 360 for golf-club business operations, and a cloud data platform that aggregates measurements across products. TrackMan exposes several developer-facing surfaces — a TrackMan Cloud GraphQL API at api.golf.trackman.com/graphql for tournaments and facility data, the TrackMan Range REST API at docs.trackmanrange.com for range/bay/session integration, a device-local TM4 WebSocket protocol for receiving live shot measurements over LAN/UPnP from a TrackMan 4 unit, and the TrackMan Baseball Data API (Swagger-documented, OAuth-client + username/password) for ingesting V3 stadium and B1 portable measurements and media. The TrackMan public GitHub organization hosts internal Unity tooling rather than client SDKs, and most developer access is partner-gated through TrackMan Sports Solutions or the Golf B2B program. The commercial model is hardware sales plus tiered software subscriptions (TrackMan Range, TrackMan 360, V3 Cloud) sold direct to teams, leagues, ranges, and consumers.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles TrackMan the way a machine reads it — 3 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — TrackMan scores 19.1/100 (emerging), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile TrackMan
Each block below is one kind of artifact we hold for TrackMan. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
TrackMan GraphQL API
GRAPHQLSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for TrackMan — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 11
Reference material describing how the API behaves
Scroll within the panel for all 11 ·
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Learn 2
Tutorials, courses, talks, and written guidance
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 8
The organization behind the API
Scroll within the panel for all 8 ·
Other 13
Properties that don't map to a standard resource type
Scroll within the panel for all 13 ·
← All providers · Data indexed from github.com/api-evangelist/trackman · machine-readable index on apis.io