Skip to main content

Catapult

Catapult signs in once for your whole organization with an OpenField API token. No athlete invitations are needed.

Connect Catapult​

  1. Get an OpenField API token from Catapult. API token is the only supported sign-in method.
  2. Add a Catapult connection and paste the token.
  3. Pick the region that hosts your tenant, then run Test connection.

What it syncs​

StreamContentsDefault
TeamsTeam definitionsOn
AthletesAthlete rosterOn
ParametersPerformance parameter definitionsOn
Parameter typesParameter type definitionsOn
PositionsPosition and role definitionsOn
Tag typesTag types for labelling entitiesOn
VenuesVenues where activities took placeOn
Threshold setsAlerting thresholds per athleteOn
ActivitiesActivity and session recordsOn
Activity athletesAthletes who took part in each sessionOn
Activity periodsPeriods and drills within each sessionOn
Stats dataAggregated metrics per athlete per periodOn
Period athletesAthlete participation per periodOff
Sensor data10 Hz GPS and IMU time seriesOff, high volume
Events dataSport-specific event detectionsOff, high volume

Opt-in streams​

Sensor data and events data are very high volume. They are off by default, and runs that include either take longer, so they are given a larger time allowance.

Period athletes is off by default too. It fans out across every activity and every period, so a first run over a long history makes many requests and the progress log can sit on one step for a while. That is normal.

Fields​

API token​

The OpenField API token issued by Catapult. It is stored encrypted.

Region​

The OpenField Connect API region that hosts your tenant: Europe, Australia, United States or China. The default is Europe.

Start time​

Optional. A Unix timestamp in seconds. Only activities at or after this time are fetched. Leave it blank for all history.

End time​

Optional. A Unix timestamp in seconds. Only activities at or before this time are fetched. Leave it blank for no upper bound.