Skip to main content

Connectors

A connector is a source of athlete data. You add one on the Connections page, then use it in a pipeline. Every connector page lists what it syncs, how it authenticates, and what each field means.

How connectors sign in​

  • Athlete consent. Each athlete approves access to their own data. You send a consent link from the Athletes page, and tokens are stored encrypted.
  • Everything else. You paste one set of credentials for your whole organization on the Connections page: an API token, an API key, a username and password, or OAuth2 client credentials. No athlete invitations are needed.

Wearables​

ConnectorWhat it syncsSign-in
GarminActivities, daily summaries, sleep and heart rateAthlete consent
WHOOPCycles, recoveries, sleeps, workouts and body measurementsAthlete consent
PolarTraining sessions, daily activity and sleepAthlete consent
Oura RingReadiness, sleep, activity, SpO2 and workoutsAthlete consent
Firstbeat SportsAthletes, teams, measurements, sessions and analysis resultsConsumer ID and shared secret

GPS and tracking​

ConnectorWhat it syncsSign-in
CatapultTeams, athletes, activities, periods and stats from OpenFieldAPI token
STATSportsSession drills and player profiles from APEX systemsAPI ID
SkillCornerTracking, physical and game intelligence dataUsername and password
Second SpectrumMatch metadata, with optional physical and tracking streamsOAuth2 client credentials

Match data​

ConnectorWhat it syncsSign-in
Hudl WyscoutSeasons, teams, players, matches, standings and match eventsUsername and password

Strength testing and athlete management​

ConnectorWhat it syncsSign-in
Kitman LabsAvailability, injuries, illnesses and wellness questionnairesOAuth2 client credentials
VALDAthlete profiles, groups and NordBord test resultsAPI key
VALD ForceDecksForceDecks tests, trials and metric definitionsOAuth2 client credentials
Hawkin DynamicsForce plate tests, athletes, teams and metric definitionsRefresh token
GymAwareVelocity based training sets, athletes and exercisesAccount ID and API token
VALD NordBord (OAuth)NordBord sessions and repetitionsOAuth2 client credentials

High-volume streams stay off until you ask​

Some streams carry a lot of data: high-frequency sensor samples, player tracking and per-sample time series. These are off by default and you enable them per pipeline. Runs that include one take longer, so they are given a larger time allowance.

Where the data goes​

Pick a destination when you create a pipeline. Each pipeline writes to its own dataset, so two connectors that both define a table with the same name never collide.