Impact Brand Python API Docs | dltHub

Impact Brand is a partnership marketing platform that offers a REST API to manage affiliates, advertisers, conversions and reports. The REST API base URL is https://api.impact.com/ and All requests require HTTP Basic authentication using the Account SID as username and Auth Token as 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 Impact Brand data in under 10 minutes.

---

What data can I load from Impact Brand?

Here are some of the endpoints you can load from Impact Brand:

---

How do I authenticate with the Impact Brand API?

Include an Authorization header generated from the Base64‑encoded "AccountSID:AuthToken" pair, or use the cURL -u option (:) for Basic auth.

1. Get your credentials

1. Log into impact.com.
2. Click your user profile in the top‑right corner.
3. Choose Settings → API.
4. Copy the Account SID and Auth Token values displayed.
5. Store them securely for use in API calls.

2. Add them to .dlt/secrets.toml

Copy
[sources.impact_brand_source]
account_sid = "your_account_sid"
auth_token = "your_auth_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 Impact Brand 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 impact_brand_pipeline.py

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

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

Inspect your pipeline and data:

Copy
dlt pipeline impact_brand_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 affiliates and campaigns from the Impact Brand 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 impact_brand_source(auth_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.impact.com/",
            "auth": {
                "type": "http_basic",
                "password": auth_token,
            },
        },
        "resources": [
            {"name": "affiliates", "endpoint": {"path": "Affiliates", "data_selector": "affiliates"}},
            {"name": "campaigns", "endpoint": {"path": "Campaigns", "data_selector": "campaigns"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="impact_brand_pipeline",
        destination="duckdb",
        dataset_name="impact_brand_data",
    )
    load_info = pipeline.run(impact_brand_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("impact_brand_pipeline").dataset()
sessions_df = data.affiliates.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM impact_brand_data.affiliates LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("impact_brand_pipeline").dataset()
data.affiliates.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 Impact Brand 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 Errors

• Problem: 401 Unauthorized response.
• Cause: Incorrect Account SID or Auth Token, or missing Basic auth header.
• Solution: Verify credentials in the Impact UI (Settings → API) and ensure they are sent as -u <AccountSID>:<AuthToken> or the appropriate Authorization header.

Rate Limiting

• Problem: 429 Too Many Requests.
• Cause: Exceeding the allowed request quota.
• Solution: Implement exponential backoff and respect the Retry-After header returned by the API.

Pagination

• Problem: Large result sets truncated.
• Cause: API returns paginated responses using page/limit or cursor parameters.
• Solution: Use the pagination fields returned in the response (e.g., next_page_token) to request subsequent pages until no token is returned.

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