Firstbeat Sports
Firstbeat signs in once for your whole organization with a consumer ID and shared secret. No athlete invitations are needed.
Connect Firstbeat Sports
- Ask Firstbeat for Cloud API access. After approval you receive a consumer ID and a shared secret.
- Collect the account IDs that Firstbeat granted to your consumer.
- Add the connection and run Test connection.
What it syncs
| Stream | Contents | Default |
|---|---|---|
| Athletes | Athlete roster across your configured accounts | On |
| Coaches | Coach users for your configured accounts | Off |
| Teams | Team definitions and athlete memberships | On |
| Measurements | Athlete measurement metadata | On |
| Sessions | Team session metadata and measurement linkage | On |
| Measurement results | Per-measurement analysis metrics | Off, high volume |
| Measurement time series | Decoded per-sample analysis vectors | Off, very high volume |
| Session results | Aggregated session analysis metrics | Off, high volume |
Opt-in streams
The three result streams are off by default. Each one needs a separate request per measurement or session, and Firstbeat limits the Cloud API to one request per second and 5,000 requests per day, resetting at midnight UTC. Runs that include a result stream take longer and are given a larger time allowance.
Heart rate zones are passed through exactly as Firstbeat reports them. In the Cloud API, zone 1 is the highest intensity zone and zone 5 the lowest.
Fields
Consumer ID
The consumer identifier Firstbeat issues once your Cloud API access is approved. If you do not have one, ask your Firstbeat contact to enable the Cloud API for your organization.
Shared secret
The shared secret issued with your consumer ID. It is stored encrypted and is used to sign each request. Ask Firstbeat for a new one if it is lost.
Account IDs
A comma-separated list of the Firstbeat account IDs your consumer may read, for example 12345, 67890. Firstbeat tells you these IDs when it grants API access. Only accounts listed here are synced.
Start date
Measurements and sessions are pulled from this date onwards, in UTC. The default is 1 January 2020.
End date
Optional. Only measurements and sessions at or before this date are synced, in UTC. Leave it blank to sync up to now.
Lookback days
How many days each run re-reads so that edits made later in Firstbeat reach your destination. The default is 7. Firstbeat has no changes feed, so a longer window catches older edits at the cost of more requests.
Time-series variables
Optional. A comma-separated list of series to decode for the measurement time series stream, for example heartRateSeries1s, artifactCorrectedRrVector. Leave it blank to use the default set. It only matters when that stream is enabled.