

Building your pipeline or Using Airbyte
Airbyte is the only open source solution empowering data teams to meet all their growing custom business demands in the new AI era.
- Inconsistent and inaccurate data
- Laborious and expensive
- Brittle and inflexible
- Reliable and accurate
- Extensible and scalable for all your needs
- Deployed and governed your way
Start syncing with Airbyte in 3 easy steps within 10 minutes
Take a virtual tour
Demo video of Airbyte Cloud
Demo video of AI Connector Builder
Setup Complexities simplified!
Simple & Easy to use Interface
Airbyte is built to get out of your way. Our clean, modern interface walks you through setup, so you can go from zero to sync in minutes—without deep technical expertise.
Guided Tour: Assisting you in building connections
Whether you’re setting up your first connection or managing complex syncs, Airbyte’s UI and documentation help you move with confidence. No guesswork. Just clarity.
Airbyte AI Assistant that will act as your sidekick in building your data pipelines in Minutes
Airbyte’s built-in assistant helps you choose sources, set destinations, and configure syncs quickly. It’s like having a data engineer on call—without the overhead.
What sets Airbyte Apart
Modern GenAI Workflows
Move Large Volumes, Fast
An Extensible Open-Source Standard
Full Control & Security
Fully Featured & Integrated
Enterprise Support with SLAs
What our users say

Andre Exner

"For TUI Musement, Airbyte cut development time in half and enabled dynamic customer experiences."

Chase Zieman

“Airbyte helped us accelerate our progress by years, compared to our competitors. We don’t need to worry about connectors and focus on creating value for our users instead of building infrastructure. That’s priceless. The time and energy saved allows us to disrupt and grow faster.”

Rupak Patel
"With Airbyte, we could just push a few buttons, allow API access, and bring all the data into Google BigQuery. By blending all the different marketing data sources, we can gain valuable insights."
Begin by accessing Strava's API to obtain the necessary data. Sign up for a Strava developer account if you haven't already and create an application to get your API client ID and client secret. Authenticate using OAuth 2.0 to obtain an access token that allows you to make authorized requests to Strava's API.
With your access token, make HTTP requests to Strava's API endpoints to retrieve the data you need. Use endpoints such as `/athlete/activities` to collect activity data. Ensure that you handle pagination if you're retrieving large datasets, as the API will return paginated results.
Once you have the raw JSON data from Strava, process and parse it into a structured format. Use a programming language like Python to extract relevant fields and convert them into a tabular format, such as CSV, to prepare for loading into TiDB.
Ensure that your TiDB environment is set up and ready to receive data. This includes installing TiDB on your server or using a cloud-based TiDB service. Confirm that you can connect to TiDB using a MySQL client or command-line tool.
Within your TiDB environment, create a new database and table structure to store the Strava data. Use SQL commands to define the schema of your table, ensuring that it matches the structure of the data you parsed from Strava. For example:
```sql
CREATE DATABASE strava_data;
USE strava_data;
CREATE TABLE activities (
id BIGINT PRIMARY KEY,
name VARCHAR(255),
distance FLOAT,
moving_time INT,
elapsed_time INT,
start_date DATETIME,
type VARCHAR(50)
);
```
Use the MySQL command-line tool or a script to load your processed data into the TiDB table. You can use the `LOAD DATA` statement or `INSERT INTO` statements if you converted the data into SQL commands. For example:
```sql
LOAD DATA LOCAL INFILE 'activities.csv' INTO TABLE activities
FIELDS TERMINATED BY ','
ENCLOSED BY '"'
LINES TERMINATED BY '\n'
IGNORE 1 ROWS;
```
After loading the data, verify that it has been correctly imported by running a few queries in TiDB. Check for data integrity and completeness. Use SQL queries to ensure that the data reflects what was retrieved from Strava and is ready for further analysis or processing. For example:
```sql
SELECT * FROM activities LIMIT 10;
```
By following these steps, you can successfully move data from Strava to TiDB without using third-party connectors or integrations.
FAQs
What is ETL?
ETL, an acronym for Extract, Transform, Load, is a vital data integration process. It involves extracting data from diverse sources, transforming it into a usable format, and loading it into a database, data warehouse or data lake. This process enables meaningful data analysis, enhancing business intelligence.
Strava is a late-stage venture company and fitness-focused social app for tracking exercise. It is one of the most popular fitness apps for those with a competitive edge. Strava is an online network where runners and cyclists can record their activities, compare performance, and compete with their community. Strava is a worldwide community of millions of runners, cyclists and triathletes, united by the fellowship of sport. Strava is a free digital service available through both mobile applications and the web.
Strava's API provides access to a wide range of data related to user activities on the platform. The following are the categories of data that can be accessed through Strava's API:
1. Athlete data: This includes information about the user's profile, such as name, age, gender, weight, and location.
2. Activity data: This includes information about the user's activities, such as distance, duration, speed, elevation, and heart rate.
3. Segment data: This includes information about the user's performance on specific segments, such as the segment name, distance, elevation, and leaderboard rankings.
4. Route data: This includes information about the user's created routes, such as the route name, distance, elevation, and map coordinates.
5. Club data: This includes information about the user's clubs, such as the club name, description, and member list.
6. Gear data: This includes information about the user's gear, such as the gear name, type, and usage statistics.
7. Authorization data: This includes information about the user's authorization status, such as access tokens and refresh tokens.
What is ELT?
ELT, standing for Extract, Load, Transform, is a modern take on the traditional ETL data integration process. In ELT, data is first extracted from various sources, loaded directly into a data warehouse, and then transformed. This approach enhances data processing speed, analytical flexibility and autonomy.
Difference between ETL and ELT?
ETL and ELT are critical data integration strategies with key differences. ETL (Extract, Transform, Load) transforms data before loading, ideal for structured data. In contrast, ELT (Extract, Load, Transform) loads data before transformation, perfect for processing large, diverse data sets in modern data warehouses. ELT is becoming the new standard as it offers a lot more flexibility and autonomy to data analysts.
What should you do next?
Hope you enjoyed the reading. Here are the 3 ways we can help you in your data journey:





