Decide which Toast API access tier — Standard (read-only), Custom, or the Partner Integrations Program (certified read/write) — is required for a given menu or order integration
domain: doc.toasttab.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Default to Standard API access if the integration only needs to read menu or order data for a single restaurant or a management group you already control — this requires no partner certification
If the use case needs data across restaurants you don't operate, or needs custom scopes beyond Standard, request Custom API access through a Toast account representative
If the integration needs to write data on behalf of restaurants that are not your own — e.g., inject third-party orders, update stock/86 status, or read/write on behalf of shared customers — apply to the Toast Partner Integrations Program
Complete the Partner Integrations Program's formal application and certification process; approved partners receive scoped OAuth credentials for read/write operations
Re-verify which tier a given endpoint requires before building — some endpoints that look read-only still require partner-tier scopes depending on the data domain
Known gotchas
Standard API access is explicitly read-only — any integration pattern that needs to push orders in or mutate menu/stock state will hit a wall on Standard credentials
Custom API access is provisioned manually by a Toast account rep, not self-serve, so lead time depends on Toast's account team responsiveness
Restaurant-level location access still has to be explicitly granted even after you have valid API credentials — a credential that works for one location may not automatically see another
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?