Sasquatch Python API Docs | dltHub

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

Last updated:

SaaSquatch is a referral and loyalty program platform that provides a REST API for managing users, referrals, rewards, and other program data. The REST API base URL is https://app.referralsaasquatch.com/api/v1/ and API requests are authenticated via HTTP Basic Auth using the API key as the 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 Sasquatch data in under 10 minutes.


What data can I load from Sasquatch?

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

ResourceEndpointMethodData selectorDescription
users/api/v1/{tenant_alias}/usersGETusersList all users in a tenant
referrals/api/v1/{tenant_alias}/referralsGETreferralsList all referrals
rewards/api/v1/{tenant_alias}/rewardGETrewardList rewards for an account
subscriptions/api/v1/{tenant_alias}/subscriptionGETsubscriptionList webhook subscriptions
export/api/v1/{tenant_alias}/export/{exportId}GETexportRetrieve a specific export

How do I authenticate with the Sasquatch API?

Authentication uses HTTP Basic Auth; include an Authorization header with a base64‑encoded string where the username is left blank and the password is the SaaSquatch API key.

1. Get your credentials

  1. Log in to the SaaSquatch dashboard.
  2. Navigate to Settings → General.
  3. Locate the API Key field and click the eye icon to reveal the key.
  4. Copy the displayed API key for use in your integration.

2. Add them to .dlt/secrets.toml

[sources.sasquatch_source] api_key = "your_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 Sasquatch 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 sasquatch_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline sasquatch_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 users and referrals from the Sasquatch 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 sasquatch_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://app.referralsaasquatch.com/api/v1/", "auth": { "type": "http_basic", "api_key": api_key, }, }, "resources": [ {"name": "users", "endpoint": {"path": "api/v1/{tenant_alias}/users", "data_selector": "users"}}, {"name": "referrals", "endpoint": {"path": "api/v1/{tenant_alias}/referrals", "data_selector": "referrals"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="sasquatch_pipeline", destination="duckdb", dataset_name="sasquatch_data", ) load_info = pipeline.run(sasquatch_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("sasquatch_pipeline").dataset() sessions_df = data.users.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM sasquatch_data.users LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("sasquatch_pipeline").dataset() data.users.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 Sasquatch 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 Errors

  • 401 Unauthorized – The API key is missing, incorrect, or not provided as the Basic Auth password. Verify that the api_key in secrets.toml matches the key shown in the SaaSquatch dashboard.

Bad Request

  • 400 Bad Request – Request parameters are malformed or required fields are missing. Check the endpoint path and query parameters against the API reference.

Not Found

  • 404 Not Found – The requested resource (e.g., a specific tenant alias, user ID, or export ID) does not exist. Ensure identifiers are correct.

Server Errors

  • 500–504 – Transient server‑side failures. Retry the request with exponential backoff.

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

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