Load Bouncer data in Python using dltHub

Build a Bouncer-to-database or-dataframe pipeline in Python using dlt with automatic Cursor support.

In this guide, we'll set up a complete Bouncer data pipeline from API credentials to your first data load in just 10 minutes. You'll end up with a fully declarative Python pipeline based on dlt's REST API connector, like in the partial example code below:

Example code
@dlt.source
def bouncer_email_verification_migration_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.usebouncer.com/v1.1/",
            "auth": {
                "type": "bearer",
                "token": access_token,
            },
        },
        "resources": [
            domain,,email/verify,,credits
            ],
    }
    [...]
    yield from rest_api_resources(config)


def get_data() -> None:
    # Connect to destination
    pipeline = dlt.pipeline(
        pipeline_name='bouncer_email_verification_migration_pipeline',
        destination='duckdb',
        dataset_name='bouncer_email_verification_migration_data', 
    )
    # Load the data
    load_info = pipeline.run(bouncer_email_verification_migration_source())
    print(load_info)

Why use dltHub Workspace with LLM Context to generate Python pipelines?

Accelerate pipeline development with AI-native context
Debug pipelines, validate schemas and data with the integrated Pipeline Dashboard
Build Python notebooks for end users of your data
Low maintenance thanks to Schema evolution with type inference, resilience and self documenting REST API connectors. A shallow learning curve makes the pipeline easy to extend by any team member
dlt is the tool of choice for Pythonic Iceberg Lakehouses, bringing mature data loading to pythonic Iceberg with or without catalogs

What you’ll do

We’ll show you how to generate a readable and easily maintainable Python script that fetches data from bouncer_email_verification_migration’s API and loads it into Iceberg, DataFrames, files, or a database of your choice. Here are some of the endpoints you can load:

Domain Verification: Verify the validity of a domain.
Email Verification: Validate email addresses to check if they are deliverable or not.
Credits: Manage and check available credits for API usage.
Toxicity List: Access lists of email addresses flagged for potential toxicity.

You will then debug the Bouncer pipeline using our Pipeline Dashboard tool to ensure it is copying the data correctly, before building a Notebook to explore your data and build reports.

Setup & steps to follow

💡
Before getting started, let's make sure Cursor is set up correctly:

We suggest using a model like Claude 3.7 Sonnet or better
Index the REST API Source tutorial: https://dlthub.com/docs/dlt-ecosystem/verified-sources/rest_api/ and add it to context as @dlt rest api
Read our full steps on setting up Cursor

Now you're ready to get started!

⚙️ Set up dlt Workspace

Install dlt with duckdb support:
```
pip install "dlt[workspace]"
```
Initialize a dlt pipeline with Bouncer support.
```
dlt init dlthub:bouncer_email_verification_migration duckdb
```
The init command will setup the necessary files and folders for the next step.

🤠 Start LLM-assisted coding

Here’s a prompt to get you started:

Prompt
Please generate a REST API Source for Bouncer API, as specified in @bouncer_email_verification_migration-docs.yaml 
Start with endpoints domain and  and skip incremental loading for now. 
Place the code in bouncer_email_verification_migration_pipeline.py and name the pipeline bouncer_email_verification_migration_pipeline. 
If the file exists, use it as a starting point. 
Do not add or modify any other files. 
Use @dlt rest api as a tutorial. 
After adding the endpoints, allow the user to run the pipeline with python bouncer_email_verification_migration_pipeline.py and await further instructions.

🔒 Set up credentials

The Bouncer API requires an API key to be included in the request headers for authentication. The API key must be provided in a header named 'x-api-key'.

To get the appropriate API keys, please visit the original source at https://www.usebouncer.com/. If you want to protect your environment secrets in a production environment, look into setting up credentials with dlt.

🏃‍♀️ Run the pipeline in the Python terminal in Cursor


python bouncer_email_verification_migration_pipeline.py

If your pipeline runs correctly, you’ll see something like the following:


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

📈 Debug your pipeline and data with the Pipeline Dashboard

Now that you have a running pipeline, you need to make sure it’s correct, so you do not introduce silent failures like misconfigured pagination or incremental loading errors. By launching the dlt Workspace Pipeline Dashboard, you can see various information about the pipeline to enable you to test it. Here you can see:
- Pipeline overview: State, load metrics
- Data’s schema: tables, columns, types, hints
- You can query the data itself
```
dlt pipeline bouncer_email_verification_migration_pipeline show
```
🐍 Build a Notebook with data explorations and reports

With the pipeline and data partially validated, you can continue with custom data explorations and reports. To get started, paste the snippet below into a new marimo Notebook and ask your LLM to go from there. Jupyter Notebooks and regular Python scripts are supported as well.
```
import dlt

data = dlt.pipeline("bouncer_email_verification_migration_pipeline").dataset()
# get omai table as Pandas frame
data.omai.df().head()
```

Running into errors?

The Bouncer API has a rate limit of 1000 requests per minute by default, which can be configured under special circumstances. Additionally, batches of email verifications are processed sequentially, requiring careful management of request timing to avoid exceeding limits. Results are retained for up to 24 hours, and each batch can contain a maximum of 100,000 emails, although a recommended size is between 1,000 to 10,000 emails.

Extra resources:

Learn more with our 1h LLM-assisted coding course!