Bonfire Networks Python API Docs | dltHub

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

Last updated:

Bonfire is a federated framework providing a Mastodon-compatible REST API and a GraphQL API for interacting with digital spaces and communities. The REST API base URL is https://<your-instance-domain>/api/v1 and most requests require a Bearer token 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 add "dlt[hub]" and start loading Bonfire Networks data in under 10 minutes.


What data can I load from Bonfire Networks?

Here are some of the endpoints you can load from Bonfire Networks:

ResourceEndpointMethodData selectorDescription
accounts/api/v1/accounts/{id}GETGet account by ID
lists/api/v1/listsGETGet all lists
list_accounts/api/v1/lists/{id}/accountsGETGet accounts in list
bonfire_groups/api/v1-bonfire/groupsGETList Bonfire groups
account_groups/api/v1-bonfire/accounts/{id}/groupsGETGet groups for account

How do I authenticate with the Bonfire Networks API?

Most endpoints require authentication using an access token passed in the Authorization header as 'Bearer '.

1. Get your credentials

Bonfire Networks uses OAuth 2.0 for programmatic API authentication, which is compatible with the Mastodon API standard. To obtain credentials: 1) Log in to your Bonfire instance via the web UI. 2) Check account settings or developer/API sections for application management to register a new application. 3) Upon registration, the instance will provide a client_id and client_secret. 4) Use these to perform the OAuth 2.0 authorization code flow (as detailed in Bonfire's authentication documentation) to exchange an authorization code for an access_token. For some instance configurations where dedicated API tokens are not exposed via UI, you may need to consult the instance administrator or use session-based authentication if applicable.

2. Add them to .dlt/secrets.toml

[sources.bonfire_networks_source] auth_token = "your_instance_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 Bonfire Networks 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 bonfire_networks_pipeline.py

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

Pipeline bonfire_networks_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset bonfire_networks_data The duckdb destination used duckdb:/bonfire_networks.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 /api/v1/accounts/verify_credentials and /api/v1/timelines/home from the Bonfire Networks 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 bonfire_networks_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://<your-instance-domain>/api/v1", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "bonfire_groups", "endpoint": {"path": "api/v1-bonfire/groups"}}, {"name": "lists", "endpoint": {"path": "api/v1/lists"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="bonfire_networks_pipeline", destination="duckdb", dataset_name="bonfire_networks_data", ) load_info = pipeline.run(bonfire_networks_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("bonfire_networks_pipeline").dataset() sessions_df = data.bonfire_groups.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM bonfire_networks_data.bonfire_groups LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("bonfire_networks_pipeline").dataset() data.bonfire_groups.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 Bonfire Networks 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.


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 Bonfire Networks?

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