Redirect Pizza Python API Docs | dltHub

Redirect Pizza is a service that allows for creating, managing, listing, and deleting redirects, email forwards, and domains via a RESTful API. The REST API base URL is https://redirect.pizza/api/v1/ and requests require a Bearer token 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 add "dlt[hub]" and start loading Redirect Pizza data in under 10 minutes.

---

What data can I load from Redirect Pizza?

Here are some of the endpoints you can load from Redirect Pizza:

---

How do I authenticate with the Redirect Pizza API?

All requests require a Bearer token passed in the Authorization header. Use the format 'Authorization: Bearer <your_api_token>' where <your_api_token> is the token generated in the account dashboard.

1. Get your credentials

Log in to your redirect.pizza dashboard. Navigate to the API section (often found under 'More' or directly via https://redirect.pizza/api). Click to generate a new API token, which will be provided in the format 'rpa_XXXXXXXXXXXXXXXXXXX'. You can assign specific scopes to the token during creation to limit access as needed.

2. Add them to .dlt/secrets.toml

Copy
[sources.redirect_pizza_source]
api_key = "rpa_your_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 init
uv add "dlt[hub]"

1. Install the dlt AI harness:

Copy
uv run dlthub 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
uv run dlthub ai toolkit install rest-api-pipeline

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 Redirect Pizza 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
uv run python redirect_pizza_pipeline.py

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

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

Inspect your pipeline and data:

Copy
uv run dlthub 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 /api/v1/redirects and /api/v1/email-forwards from the Redirect Pizza 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 redirect_pizza_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://redirect.pizza/api/v1/",
            "auth": {"type": "bearer", "token": access_token},
        },
        "resources": [
            {"name": "redirects", "endpoint": {"path": "api/v1/redirects"}},
            {"name": "email_forwards", "endpoint": {"path": "api/v1/email-forwards"}}
        ],
    }
    yield from rest_api_resources(config)


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

SQL (DuckDB example):

Copy
SELECT * FROM redirect_pizza_data.redirects LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("redirect_pizza_pipeline").dataset()
data.redirects.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 Redirect Pizza 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.

---

Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI harness:

• data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
• dlthub-platform — Deploy, schedule, and monitor your pipeline in production.

Copy
uv run dlthub ai toolkit install data-exploration
uv run dlthub ai toolkit install dlthub-platform

• 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