Aweber Python API Docs | dltHub

AWeber is an email marketing platform that provides a REST API for managing accounts, lists, subscribers, campaigns, broadcasts and related email analytics. The REST API base URL is https://api.aweber.com/1.0 and All requests use OAuth 2.0 (scoped access tokens)..

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

---

What data can I load from Aweber?

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

---

How do I authenticate with the Aweber API?

The API uses OAuth 2.0; request flows obtain an access token which must be sent in the Authorization header as: Authorization: Bearer {access_token}. Scopes (e.g. subscriber.read, email.read, email.write) control endpoint access.

1. Get your credentials

1. Register your application in the AWeber developer / apps area to obtain a client_id and client_secret; 2) Build an OAuth 2.0 authorization URL including required scopes and redirect_uri; 3) Have the AWeber account owner authorize the app and capture the authorization code; 4) Exchange the authorization code for an access token via the token endpoint; 5) Use the access token in Authorization: Bearer {token}; refresh tokens can be used per OAuth flow.

2. Add them to .dlt/secrets.toml

Copy
[sources.aweber_source]
client_id = "your_client_id"
client_secret = "your_client_secret"
access_token = "your_access_token"
refresh_token = "your_refresh_token"

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:

Copy
uv venv && source .venv/bin/activate
uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

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

Copy
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 Aweber 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:

Copy
python aweber_pipeline.py

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

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

Inspect your pipeline and data:

Copy
dlt pipeline aweber_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 lists and subscribers from the Aweber API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def aweber_source(oauth_client=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.aweber.com/1.0",
            "auth": {
                "type": "bearer",
                "access_token": oauth_client,
            },
        },
        "resources": [
            {"name": "lists", "endpoint": {"path": "accounts/{accountId}/lists", "data_selector": "entries"}},
            {"name": "subscribers", "endpoint": {"path": "accounts/{accountId}/lists/{listId}/subscribers", "data_selector": "entries"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="aweber_pipeline",
        destination="duckdb",
        dataset_name="aweber_data",
    )
    load_info = pipeline.run(aweber_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):

Copy
import dlt

data = dlt.pipeline("aweber_pipeline").dataset()
sessions_df = data.subscribers.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM aweber_data.subscribers LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("aweber_pipeline").dataset()
data.subscribers.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 Aweber data to?

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

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 401 Unauthorized, verify that the Authorization header is present: Authorization: Bearer {access_token}. Ensure token has not expired and has the required scopes (e.g. subscriber.read or email.read). If expired, refresh the access token using the refresh_token.

Rate limits and request throttling

AWeber documents standard API usage limits; if you receive 429 Too Many Requests, back off and retry after the window. Use pagination to avoid large single requests.

Pagination quirks

Most collection endpoints return paginated collections; the list of records is contained under the response key "entries". Use the provided pagination links in responses (next/prev) or query params (ws.size, ws.start) and ws.op=find for search endpoints.

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.

Copy
dlt ai toolkit data-exploration install
dlt ai toolkit dlthub-runtime install

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack