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
| Connector | What it syncs | Sign-in |
|---|---|---|
 Garmin | Activities, daily summaries, sleep and heart rate | Athlete consent |
| WHOOP | Cycles, recoveries, sleeps, workouts and body measurements | Athlete consent |
| Polar | Training sessions, daily activity and sleep | Athlete consent |
| Oura Ring | Readiness, sleep, activity, SpO2 and workouts | Athlete consent |
GPS and tracking
| Connector | What it syncs | Sign-in |
|---|---|---|
 Catapult | Teams, athletes, activities, periods and stats from OpenField | API token |
| STATSports | Session drills and player profiles from APEX systems | API ID |
 SkillCorner | Tracking, physical and game intelligence data | Username and password |
 Second Spectrum | Match metadata, with optional physical and tracking streams | OAuth2 client credentials |
Strength testing and athlete management
| Connector | What it syncs | Sign-in |
|---|---|---|
 Kitman Labs | Availability, injuries, illnesses and wellness questionnaires | OAuth2 client credentials |
| VALD | Athlete profiles, groups and NordBord test results | API key |
| VALD NordBord (OAuth) | NordBord sessions and repetitions | OAuth2 client credentials |
High-volume streams stay off until you ask
Some streams carry a lot of data: raw GPS and IMU samples, 10 Hz sensor data, player tracking and intraday heart rate. 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.