Partnerstack Python API Docs | dltHub

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

Last updated:

Partnerstack is a partner management platform exposing a REST API to manage partners, customers, rewards, transactions, and programs. The REST API base URL is https://api.partnerstack.com/api/v2 and all requests require a Bearer token (API key) in the Authorization 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 Partnerstack data in under 10 minutes.


What data can I load from Partnerstack?

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

ResourceEndpointMethodData selectorDescription
customers/customersGETdata.itemsList customers (paginated)
customer/customers/{customer_key}GETdataRetrieve a single customer
partners/partnersGETdata.itemsList partners (paginated)
partner/partners/{partner_key}GETdataRetrieve a single partner
rewards/rewardsGETdata.itemsList rewards (paginated)
transactions/transactionsGETdata.itemsList transactions (paginated)
programs/programsGETdata.itemsList marketplace programs (paginated)
partnerships/partnershipsGETdata.itemsList partnerships (paginated)
payouts/payoutsGETdata.itemsList payouts (paginated)

How do I authenticate with the Partnerstack API?

Authenticate using a Partnerstack API key via Bearer token: set header Authorization: Bearer {api_key}. API keys are available in the Partner dashboard Settings → API.

1. Get your credentials

  1. Log in to your Partnerstack dashboard at https://dash.partnerstack.com.
  2. Navigate to Settings → API.
  3. Click “Reveal” on your existing API key or create a new one.
  4. Copy the key and use it as the Bearer token in requests or store it in dlt secrets.

2. Add them to .dlt/secrets.toml

[sources.partnerstack_source] api_key = "your_partnerstack_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 Partnerstack 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 partnerstack_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline partnerstack_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 partners and transactions from the Partnerstack 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 partnerstack_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.partnerstack.com/api/v2", "auth": { "type": "bearer", "token": api_key, }, }, "resources": [ {"name": "partners", "endpoint": {"path": "partners", "data_selector": "data.items"}}, {"name": "transactions", "endpoint": {"path": "transactions", "data_selector": "data.items"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="partnerstack_pipeline", destination="duckdb", dataset_name="partnerstack_data", ) load_info = pipeline.run(partnerstack_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("partnerstack_pipeline").dataset() sessions_df = data.partners.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM partnerstack_data.partners LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("partnerstack_pipeline").dataset() data.partners.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 Partnerstack 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

If you receive 401 Unauthorized, verify your API key and ensure your requests include header Authorization: Bearer {api_key}. Obtain or reveal the key in Settings → API.

Rate limits and pagination

List endpoints are paginated using starting_after, ending_before, and limit. Use the last item's key from data.items as starting_after to fetch the next page. Check data.has_more to know if additional pages exist.

Common HTTP errors

  • 400 Bad Request – invalid parameters.
  • 401 Unauthorized – missing or invalid API key.
  • 403 Forbidden – insufficient permissions.
  • 404 Not Found – invalid resource identifier.
  • 500 Internal Server Error – server-side issue; retry later.

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

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