Fanbridge Python API Docs | dltHub

Build a Fanbridge-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

Fanbridge is a marketing platform that offers a custom, private REST API for partners. The REST API base URL is No public base URL; API endpoint is provided to customers upon request. and Authentication is performed with an API key (or Bearer token) sent in the Authorization header..

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 pip install "dlt[workspace]" and start loading Fanbridge data in under 10 minutes.


What data can I load from Fanbridge?

Here are some of the endpoints you can load from Fanbridge:

ResourceEndpointMethodData selectorDescription
networksnetworksGETList network objects (placeholder)
containerscontainersGETList container objects (placeholder)
sessionssessionsGETList session objects (placeholder)
projectsprojectsGETList project objects (placeholder)
usersusersGETList user objects (placeholder)

How do I authenticate with the Fanbridge API?

Requests must include an API key (or Bearer token) in the Authorization header, e.g., Authorization: Bearer <API_KEY>.

1. Get your credentials

  1. Log in to your Fanbridge (Kit) account dashboard.
  2. Navigate to the "Partner Portal" or "API Settings" section.
  3. Submit a request for API access if not already granted.
  4. Once approved, locate the generated API key/token in the dashboard.
  5. Copy the key and store it securely for use in dlt configurations.

2. Add them to .dlt/secrets.toml

[sources.fanbridge_source] api_key = "YOUR_API_KEY"

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 venv && source .venv/bin/activate uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

dlt 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:

dlt ai toolkit rest-api-pipeline install

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 Fanbridge 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:

python fanbridge_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline fanbridge_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset fanbridge_data The duckdb destination used duckdb:/fanbridge.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

dlt pipeline fanbridge_pipeline 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 networks and containers from the Fanbridge 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 fanbridge_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "No public base URL; API endpoint is provided to customers upon request.", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "networks", "endpoint": {"path": "networks"}}, {"name": "containers", "endpoint": {"path": "containers"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="fanbridge_pipeline", destination="duckdb", dataset_name="fanbridge_data", ) load_info = pipeline.run(fanbridge_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("fanbridge_pipeline").dataset() sessions_df = data.networks.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM fanbridge_data.networks LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("fanbridge_pipeline").dataset() data.networks.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 Fanbridge data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

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


Troubleshooting

Authentication failures

If you receive a 401 Unauthorized response, verify that the API key is correct, has not expired, and is being sent in the Authorization header as a Bearer token.

Rate limits

The API enforces a limit of 1000 requests per hour. Exceeding this limit returns a 429 Too Many Requests response. Implement exponential back‑off or respect the Retry-After header to avoid throttling.

Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-runtime — Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install

Was this page helpful?

Community Hub

Need more dlt context for Fanbridge?

Request dlt skills, commands, AGENT.md files, and AI-native context.