Bloomerang Python API Docs | dltHub

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

Last updated:

Bloomerang's REST API is for server-to-server integrations, requiring a private key. It supports data push and pull from Bloomerang's database. The latest version is v2, with detailed documentation available. The REST API base URL is https://api.bloomerang.com/v1 and All requests require the Bloomerang private API key supplied using HTTP Basic‑style Authorization (API key as username, blank password)..

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 Bloomerang data in under 10 minutes.


What data can I load from Bloomerang?

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

ResourceEndpointMethodData selectorDescription
constituents/ConstituentGETResultsList constituents (supports skip/take paging, filters).
constituent/Constituent/{id}GETRetrieve single constituent by id (single object response).
fund/FundGETResultsList all funds (response: Total, Start, MaxItems, Results).
campaign/CampaignGETResultsList campaigns (response contains Results array).
appeal/AppealGETResultsList appeals.
custom_field/CustomField/{Type}GETResultsList custom fields for a given type e.g. CustomField/Constituent.
user/UserGETResultsList users (response includes Start, MaxItems, Total, Results).
transaction/TransactionGETResultsList transactions (timeline/transaction endpoints exist).
email/Email/{id}GETRetrieve a single email record.
address/Address/{id}GETRetrieve a single address record.

How do I authenticate with the Bloomerang API?

The API uses a private key for server‑to‑server access. Supply the key in the Authorization header as Basic <api_key>: (do not base64‑encode); in request examples the header is "Authorization: Basic {API_KEY}:".

1. Get your credentials

  1. Log in to Bloomerang as an Administrator. 2) Click the user icon (top‑right) → Edit My User / User Settings. 3) Generate a new API key (v2.0 key may be created from crm.bloomerang.co user settings). 4) Copy and securely store the private API key; use it for all API calls. For third‑party access, register an OAuth app as documented.

2. Add them to .dlt/secrets.toml

[sources.bloomerang_source] api_key = "your_bloomerang_private_api_key_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 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 Bloomerang 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 bloomerang_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline bloomerang_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 constituents and transaction from the Bloomerang 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 bloomerang_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.bloomerang.com/v1", "auth": { "type": "http_basic", "api_key": api_key, }, }, "resources": [ {"name": "constituents", "endpoint": {"path": "Constituent", "data_selector": "Results"}}, {"name": "fund", "endpoint": {"path": "Fund", "data_selector": "Results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="bloomerang_pipeline", destination="duckdb", dataset_name="bloomerang_data", ) load_info = pipeline.run(bloomerang_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("bloomerang_pipeline").dataset() sessions_df = data.constituents.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM bloomerang_data.constituents LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("bloomerang_pipeline").dataset() data.constituents.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 Bloomerang 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 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 Bloomerang?

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