Sendinblue Python API Docs | dltHub

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

Last updated:

Sendinblue is a cloud‑based email marketing and transactional email service platform. The REST API base URL is https://api.sendinblue.com/v3 and All requests require an API key passed in the 'api-key' 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 Sendinblue data in under 10 minutes.


What data can I load from Sendinblue?

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

ResourceEndpointMethodData selectorDescription
contacts/contactsGETcontactsGet all contacts (paginated)
contacts_lists/contacts/listsGETlistsGet all contact lists
contacts_list_contacts/contacts/lists/{listId}/contactsGETcontactsGet contacts in a list
account/accountGETGet account information and credits
contacts_attributes/contacts/attributesGETattributesList contact attributes

How do I authenticate with the Sendinblue API?

Include the HTTP header 'api-key: YOUR_KEY' and set 'content-type: application/json' on each request.

1. Get your credentials

  1. Log in to your Sendinblue account.
  2. Navigate to SMTP & API (Account > SMTP & API or Settings > API).
  3. Click Create a new API key and ensure the version column shows "v3".
  4. Copy the generated key and store it securely.
  5. Use this key in the 'api-key' request header.

2. Add them to .dlt/secrets.toml

[sources.sendinblue_source] api_key = "your_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 Sendinblue 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 sendinblue_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline sendinblue_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 contacts and email_campaigns from the Sendinblue 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 sendinblue_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.sendinblue.com/v3", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "contacts", "endpoint": {"path": "contacts", "data_selector": "contacts"}}, {"name": "email_campaigns", "endpoint": {"path": "emailCampaigns", "data_selector": "campaigns"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="sendinblue_pipeline", destination="duckdb", dataset_name="sendinblue_data", ) load_info = pipeline.run(sendinblue_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("sendinblue_pipeline").dataset() sessions_df = data.contacts.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM sendinblue_data.contacts LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("sendinblue_pipeline").dataset() data.contacts.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 Sendinblue 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

401 Unauthorized if API key missing or invalid; verify the api-key header.

Rate limits

429 Too Many Requests; check response headers for remaining quota and retry after the specified reset time.

Pagination

Endpoints return paginated results using limit/offset (or page) parameters; inspect the count and total fields and the array key (e.g., contacts).

Validation/Bad requests

400 Bad Request for malformed payloads; error details are provided in the JSON response under an error field.

Server errors

5xx responses indicate server‑side issues; implement exponential backoff and retry.

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 Sendinblue?

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