Hudl
Hudl is a Lincoln, Nebraska sports performance and analytics technology company founded in 2007. The company started as a video sharing and review platform for high school, college, and professional teams and has grown into a global provider of video capture hardware, performance analysis software, and sports data services. Hudl operates across basketball, baseball, football, ice hockey, rugby, soccer, softball, and volleyball, serving customers from youth clubs through professional leagues. The company's product portfolio spans the core Hudl video platform, Hudl Focus AI-powered capture cameras (Indoor, Outdoor, Flex, Point), Hudl Replay and Hudl Studio for live and tactical analysis, Hudl IQ for American football analytics, Volleymetrics, the Hudl TV livestreaming product, and Hudl Tickets digital ticketing. Through acquisitions Hudl has consolidated several leading performance analysis and football data brands under its umbrella, including Sportscode (performance analysis software), Wyscout (the largest soccer video and stats database), Statsbomb (advanced football analytics), Instat (video and scouting), WIMU and Titan (athlete tracking and wearables), and Signal and ADI. Hudl exposes commercial developer surfaces primarily through Hudl Wyscout (Wyscout Data API, documented as OpenAPI 3.0 at apidocs.wyscout.com, with Database, Stats, Events, and Physical Data packs) and Hudl Statsbomb (the Statsbomb Aggregated API for player-match, player-season, team-match, and team-season data, accessed via the Data Hub, plus the Raw X&Y Tracking Data API and a Wyscout/Statsbomb ID Mapping API). Core Hudl video and Hudl Focus do not publish a public developer API; B2B integrations are sales-mediated. Hudl maintains a public GitHub organization (github.com/hudl) with infrastructure, resilience, and media tooling open source projects (Mjolnir, Fargo, HudlFfmpeg, react-native components), but these are engineering libraries, not product SDKs. Hudl's revenue model is SaaS subscriptions for video, analytics, and data packages, plus camera hardware sales and data licensing.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Hudl the way a machine reads it — 2 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 — Hudl scores 12.4/100 (minimal), 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 Hudl
Each block below is one kind of artifact we hold for Hudl. 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.
Security 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 Hudl — 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.
Documentation 1
Reference material describing how the API behaves
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 3
Status, limits, changes, and where to get help
Company 6
The organization behind the API
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/hudl · machine-readable index on apis.io