Bumble Python API Docs | dltHub
Build a Bumble-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Bumble does not provide a public REST API, and any available integrations rely on unofficial reverse-engineered endpoints. The REST API base URL is https://api.gotinder.com and all requests require a custom header token for authentication.
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading Bumble data in under 10 minutes.
What data can I load from Bumble?
Here are some of the endpoints you can load from Bumble:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| profile | /me/profile | GET | Get the authenticated user's profile information. | |
| matches | /matches | GET | Get a list of the user's current matches. | |
| encounters | /encounters | GET | Get a list of suggested profiles (encounters). | |
| messages | /chat/{match_id}/messages | GET | Get the chat history for a specific match. | |
| auth_request | /auth/request-phone-verification | POST | Initiate phone verification (request OTP). | |
| auth_verify | /auth/verify-phone | POST | Complete phone verification and obtain access token. |
How do I authenticate with the Bumble API?
Authentication requires a token (often referred to as an X-Auth-Token) which must be included in the request headers. This token is typically obtained through specific authentication endpoints after providing valid credentials.
1. Get your credentials
Bumble does not provide an official public REST API or a developer dashboard for generating API keys. Access is achieved by reverse-engineering the web or mobile client. To obtain credentials: 1. Log in to the Bumble web client in your browser. 2. Open browser developer tools (Network tab). 3. Perform an action (e.g., refresh the page) and inspect the outgoing requests to identify a request containing an authentication token (typically labeled X-Auth-Token in the headers). 4. Copy this token value to use as your api_key for authentication. Note that this method is unofficial and requires manual token refreshing as these tokens may expire.
2. Add them to .dlt/secrets.toml
[sources.bumble_source] api_key = "your_extracted_x_auth_token_here"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
uv run dlthub ai toolkit install rest-api-pipeline
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the Bumble API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
uv run python bumble_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline bumble_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset bumble_data The duckdb destination used duckdb:/bumble.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads v2/recs/core and v2/matches from the Bumble API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def bumble_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.gotinder.com", "auth": {"type": "api_key", "api_key": api_key, "name": "X-Auth-Token", "location": "header"}, }, "resources": [ {"name": "matches", "endpoint": {"path": "matches"}}, {"name": "encounters", "endpoint": {"path": "encounters"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="bumble_pipeline", destination="duckdb", dataset_name="bumble_data", ) load_info = pipeline.run(bumble_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("bumble_pipeline").dataset() sessions_df = data.matches.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM bumble_data.matches LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("bumble_pipeline").dataset() data.matches.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load Bumble data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for Bumble?
Request dlt skills, commands, AGENT.md files, and AI-native context.