Katapult Python API Docs | dltHub
Build a Katapult-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
The Katapult API uses REST protocol for verification, requiring SMS code submission to verify phone numbers. Authentication requires a secret generated via the Katapult Console. API tokens are bearer tokens in the Authorization header. The REST API base URL is https://www.katapult.com/api/v3 and All requests require a Bearer OAuth access 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 pip install "dlt[workspace]" and start loading Katapult data in under 10 minutes.
What data can I load from Katapult?
Here are some of the endpoints you can load from Katapult:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| application | /application/{uid} | GET | Retrieve an application by UID (returns application object) | |
| application_preapprove | /application/{uid}/preapprove | GET | Check preapproval status for an application | |
| application_confirm_order | /application/{uid}/confirm_order | POST | Confirm order for application (included for relevance) | |
| application_delivery | /application/{uid}/delivery | POST | Submit delivery information for an application | |
| user_auth_verify | /user/auth/verify | POST | Submit phone verification code (auth flow) | |
| user_auth_retailer | /user/auth/retailer | POST | Request verification code by phone (auth flow) | |
| merchant_profiles | /merchant_profiles | GET | (If available) list merchant profiles — docs do not show explicit response array key | |
| applications_search | /applications | GET | (If available) list/search applications — data selector not documented publicly |
How do I authenticate with the Katapult API?
Acquire an OAuth access token (provided via the Katapult Console during onboarding). Send it in the Authorization header: Authorization: Bearer {token}. All requests and responses use JSON and must be made over HTTPS.
1. Get your credentials
- During onboarding, receive OAuth credentials from your Katapult Integrations Engineer or Console. 2) In the Katapult Console, generate an API access token for the desired environment (sandbox or live). 3) Copy the token and store it securely; use it in the Authorization header as a Bearer token for all requests.
2. Add them to .dlt/secrets.toml
[sources.katapult_source] token = "your_oauth_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:
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 Katapult 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 katapult_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline katapult_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset katapult_data The duckdb destination used duckdb:/katapult.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline katapult_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 application and applications from the Katapult 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 katapult_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://www.katapult.com/api/v3", "auth": { "type": "bearer", "token": token, }, }, "resources": [ {"name": "application", "endpoint": {"path": "application/{uid}"}}, {"name": "applications", "endpoint": {"path": "applications"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="katapult_pipeline", destination="duckdb", dataset_name="katapult_data", ) load_info = pipeline.run(katapult_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("katapult_pipeline").dataset() sessions_df = data.application.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM katapult_data.application LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("katapult_pipeline").dataset() data.application.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 Katapult data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example 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.
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 Katapult?
Request dlt skills, commands, AGENT.md files, and AI-native context.