Toast Python API Docs | dltHub
Build a Toast-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Toast's REST APIs provide access to configuration, orders, inventory, and transaction data for restaurant locations. They use HTTP requests and return standard responses and error codes. The enterprise module allows multi-location sharing of configurations. The REST API base URL is https://[toast-api-hostname] and all requests require a Bearer token obtained from the /authentication/v1/authentication/login endpoint.
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 Toast data in under 10 minutes.
What data can I load from Toast?
Here are some of the endpoints you can load from Toast:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| menus | /openapi/menus/overview | GET | Retrieve fully resolved menus for a location | |
| orders | /openapi/orders/ | GET | items | List orders placed at the restaurant |
| restaurants | /openapi/restaurants/ | GET | data | Retrieve restaurant details and configuration |
| employees | /openapi/employees/ | GET | employees | List employee records for the restaurant |
| authentication_login | /authentication/v1/authentication/login | POST | Obtain a JWT token using client‑credentials flow |
How do I authenticate with the Toast API?
Toast uses OAuth2 client‑credentials authentication. POST a JSON body with clientId, clientSecret and userAccessType="TOAST_MACHINE_CLIENT" to /authentication/v1/authentication/login and include the returned JWT in the Authorization header as "Bearer ", plus the Toast-Restaurant-External-ID header to set the restaurant context.
1. Get your credentials
- Contact your Toast account representative or Toast support to request an API clientId and clientSecret for your restaurant.
- Store the credentials securely (do not commit them to source control).
- Obtain an authentication token by POSTing to https://[toast-api-hostname]/authentication/v1/authentication/login with a JSON body containing {"clientId":"","clientSecret":"","userAccessType":"TOAST_MACHINE_CLIENT"}.
- Use the returned JWT as a Bearer token in the Authorization header for all subsequent API calls.
2. Add them to .dlt/secrets.toml
[sources.toast_source] client_id = "your_client_id_here" client_secret = "your_client_secret_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 Toast 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 toast_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline toast_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset toast_data The duckdb destination used duckdb:/toast.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline toast_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 menus and authentication_login from the Toast 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 toast_source(client_credentials=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://[toast-api-hostname]", "auth": { "type": "bearer", "token": client_credentials, }, }, "resources": [ {"name": "menus", "endpoint": {"path": "openapi/menus/overview"}}, {"name": "authentication_login", "endpoint": {"path": "authentication/v1/authentication/login"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="toast_pipeline", destination="duckdb", dataset_name="toast_data", ) load_info = pipeline.run(toast_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("toast_pipeline").dataset() sessions_df = data.menus.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM toast_data.menus LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("toast_pipeline").dataset() data.menus.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 Toast 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 Toast?
Request dlt skills, commands, AGENT.md files, and AI-native context.