Getting started

KoraBridge moves data from sports devices and vendor APIs into the warehouse, database or bucket your analysts already use. You set it up in four steps: add connections, invite athletes if your source needs it, create a pipeline, and optionally put it on a schedule.

Step	What you do	When
1. Add connections	Store credentials for one source and one destination	Always
2. Invite athletes	Send consent links to athletes	Only for per-athlete sources
3. Create a pipeline	Pair a source with a destination and pick streams	Always
4. Add a schedule	Run the pipeline on a timer	Optional

1. 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 such as WHOOP, Catapult or Kitman Labs, 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, such as PostgreSQL, Snowflake or Amazon S3, 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

PostgreSQL, Lakebase, Databricks and Amazon S3 destinations run a live check. They load a small test row, or write and delete 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.

2. Invite athletes

This step applies only to connectors that authenticate per athlete: WHOOP, Garmin, Polar and Oura. 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. KoraBridge 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.

3. 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.

4. 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.

Which connectors need athlete consent

Authentication	Connectors
Per athlete (consent link)	WHOOP, Garmin, Polar, Oura
Organization level (API key, HTTP Basic or client credentials)	Catapult, VALD, VALD NordBord, STATSports, Kitman Labs, SkillCorner, Second Spectrum

Where to go next

• Pipelines and scheduling: runs, statuses, schedules and troubleshooting.
• API reference: drive KoraBridge from your own code.