Skip to main content

Getting started

KeyStride Bridge moves data from sports devices and vendor APIs into the warehouse, database or bucket your analysts already use. You set it up in a few steps: add connections, create a pipeline, and optionally put it on a schedule.

Some sources also need each athlete to approve access first. That step comes after the connections.

Add connections​

A connection holds the credentials for one source or one destination. You need at least one of each before you can create a pipeline.

  1. Open Connections from the sidebar.
  2. Choose Add connection and pick a source connector, then fill in its credentials and settings. Each connector page explains where to find every value. See Connectors.
  3. Choose Add connection again and pick where the data should land, then enter the connection details. See Destinations.
  4. Choose Test and create to store the connection and test it in one go, or Save without testing to store it now and test later.
What a passing test proves

Where a destination supports it, the test runs a live check. It loads a small test row, or writes and deletes a small test object, so a passing test means the pipeline can really write there. These tests finish in the background, so the page shows the result when it is ready. Other destinations check that the details you entered are well formed.

Credentials are encrypted at rest with a key that belongs to your organization alone. See Security and data handling. You can add as many sources and destinations as you need.

Invite athletes​

This step applies only to connectors that authenticate per athlete: Garmin, WHOOP, Polar and Oura Ring. Each athlete has to approve access to their own data before it can be synced.

  1. Open Athletes from the sidebar.
  2. Enter the athlete's email address, select the connector, and choose Invite.
  3. KeyStride Bridge generates a unique consent link. Copy it and send it to the athlete.
  4. The athlete opens the link and approves access. Their tokens are stored encrypted, and the consent status changes from pending to approved.

You can revoke an athlete's consent at any time from the Athletes page.

Every other connector authenticates for your whole organization, with an API key, HTTP Basic or OAuth2 client credentials. For those, adding the credentials on the Connections page is enough and nobody needs to be invited.

Create a pipeline​

A pipeline moves data from one source connection to one destination connection.

  1. Open Pipelines from the sidebar and choose New pipeline.
  2. Name it and select the source connection and the destination connection.
  3. Choose which streams to sync. Each connector offers a set of streams, which become tables in your destination. Sensible defaults are pre-selected. High-volume streams such as raw GPS or IMU samples, tracking data and per-sample time series are opt-in, because they can be very large.
  4. Choose Run now to start a one-off sync. The pipeline page shows its status as it progresses.

Every pipeline writes to its own isolated dataset in the destination, so two pipelines never share a schema or overwrite each other's tables. You can reuse one source connection in several pipelines. Where a connector and stream support it, data loads incrementally, so later runs fetch only what is new or changed.

Automate with a schedule​

Once a manual run looks right, put the pipeline on a schedule so nobody has to trigger it by hand. Schedules, timing rules and what to do when a run fails are covered in Pipelines and scheduling.

These connectors sign in per athlete, with a consent link: Garmin, WHOOP, Polar and Oura Ring. Every other connector uses one set of credentials for your whole organization (an API key, HTTP Basic or client credentials), so nobody needs to be invited.

Where to go next​