ReferralHero Python API Docs | dltHub

ReferralHero is a referral marketing platform that provides a REST API to manage campaigns, subscribers, referrals, rewards, transactions and coupon groups. The REST API base URL is https://app.referralhero.com/api/v2 and All requests require an API token sent in request headers (Bearer or X-API-Key)..

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

---

What data can I load from ReferralHero?

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

---

How do I authenticate with the ReferralHero API?

Authentication uses an API token. Preferred header: Authorization: Bearer YOUR_API_TOKEN. Alternative header: X-API-Key: YOUR_API_TOKEN.

1. Get your credentials

1. Log in to the ReferralHero dashboard. 2) Navigate to Account > API (or Settings > API). 3) Copy the API Token shown. 4) Keep the token secret and use it in the Authorization header.

2. Add them to .dlt/secrets.toml

Copy
[sources.referral_hero_source]
api_token = "your_api_token_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:

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 ReferralHero 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 referral_hero_pipeline.py

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

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

Inspect your pipeline and data:

Copy
dlt pipeline referral_hero_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 ReferralHero 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 referral_hero_source(api_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://app.referralhero.com/api/v2",
            "auth": {
                "type": "api_key",
                "api_token": api_token,
            },
        },
        "resources": [
            {"name": "lists", "endpoint": {"path": "lists", "data_selector": "data"}},
            {"name": "subscribers", "endpoint": {"path": "lists/:uuid/subscribers", "data_selector": "data.subscribers"}}
        ],
    }
    yield from rest_api_resources(config)


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

SQL (DuckDB example):

Copy
SELECT * FROM referral_hero_data.subscribers LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("referral_hero_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 ReferralHero 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 HTTP 401 or an error code "no_token", ensure the API token is sent in the Authorization: Bearer YOUR_API_TOKEN header or X-API-Key header. Verify the token is active in the dashboard.

Rate limits

ReferralHero enforces a soft limit (e.g., 5,000 calls per hour). Exceeding this returns HTTP 429 with error code "too_many_calls". Implement exponential backoff and respect the per‑hour quota.

Pagination

GET endpoints are paginated. Responses contain a pagination object (total_pages, current_page, per_page, total_objects) and the records array under data (e.g., data.subscribers). Use page and per_page query parameters to navigate pages.

Common API error responses

• 400/422: Validation errors – response includes status/message and an error code such as "subscriber_not_found".
• 401: Missing or invalid token – error code "no_token".
• 403: Forbidden – insufficient privileges.
• 404: Resource not found – check UUIDs and IDs.
• 429: Rate limit exceeded – error code "too_many_calls".
• 500: Server error – retry with backoff and contact support.

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