# Toast integration for multi-brand restaurant groups

Connect Toast to your ordering app, master menu, franchise reports and the other POS systems in your group. Here is what the Toast API reads and writes, how access works and where it breaks.

- **API**: REST, webhooks, JWT auth
- **Access**: Partner, custom, or read-only Standard API
- **Limit**: 20 requests a second
- **Markets**: US, Canada, UK, Ireland, Australia

**In short.** A Toast integration connects the Toast POS to other systems through its REST API: menus and restaurant data out, orders in, sales out to reports. Read-only access comes with Restaurant Management Suite Essentials; writing orders, labor or stock needs a custom integration or Toast partner status. The API allows 20 requests a second, and Toast retries a failed webhook only twice, so connectors need their own checks. dev.family builds Toast connectors for groups and keeps them running under an SLA.

## What a Toast integration moves

Read means we can get it from Toast. Write means we can send it to Toast.

| Object | Read | Write | What the API supports |
| --- | --- | --- | --- |
| Menus and prices | Yes | No | Menus API is read-only; 1 request a second per location |
| Orders | Yes | Yes | Read by webhook or in bulk; write needs a custom or partner integration |
| Labor and stock | Yes | Yes | Shifts, time entries and item stock levels |
| Restaurant setup and kitchen | Yes | No | Configuration, kitchen and cash management data |
| Sales reporting | Yes | No | Analytics API, a separate set of credentials |
| Loyalty and gift cards | Partly | Partly | Outbound: Toast calls your endpoint at checkout. No guest API found in the docs |

## How groups connect Toast

- **Own app into Toast**: Your app ⇄ Toast ⇄ Kitchen screens. Orders from your app land in the right Toast location and on the kitchen screen.
- **Delivery in one feed**: [DoorDash Drive](https://dev.family/foodtech/integrations/doordash-drive) ⇄ [Deliverect](https://dev.family/foodtech/integrations/deliverect) ⇄ Toast. Marketplace orders and menus run through middleware into Toast.
- **Toast next to other POS**: Toast ⇄ [Lightspeed](https://dev.family/foodtech/integrations/lightspeed) ⇄ One report. After an acquisition, Toast sales sit next to another POS in one warehouse and one item list.

## How Toast API access works

Toast offers four routes. Standard API access is read-only and self-serve: a location on Restaurant Management Suite Essentials or higher creates credentials in Toast Web. A custom integration lets a Toast customer's own or trusted developers read and write. Analytics API access is a separate credential set for reporting. Partner status is for software companies that sell to many Toast restaurants.

For a restaurant group, the first two cover almost everything. You don't need partner status to connect your own locations.

Docs: doc.toasttab.com · API release notes and update announcements · checked November 9, 2026

**What we need from you**

- Toast admin access with the Manage Integrations permission
- Your Toast plan per location
- Which locations and brands to connect
- A test location

**Getting access:** Standard API credentials are self-serve in Toast Web; a custom integration goes through your Toast account rep.

**Not sure what your contract allows?** Send us the systems and the data you need. We'll tell you which access route fits and what the connector involves.

## Where Toast integrations break

- **Tight menu limits.**: Toast allows 20 requests a second and 10,000 per 15 minutes overall, but menus only once a second per location. Syncing menus for a whole group needs a queue.
- **Two webhook retries.**: Toast retries a failed webhook at five and ten minutes, then stops. Missed order events have to be caught by a bulk read, limited to five requests a second and one-month windows.
- **Write access isn't standard.**: Read-only credentials can't create orders. Order injection needs a custom integration or partner status, so plan access before the build.
- **No guest API.**: Loyalty and gift cards run through endpoints you host, and we found no guest or customer API in the docs. Guest data needs its own design.
- **Changes with 30 to 90 days' notice.**: Toast announces API changes with planned dates; recent lead times ran about a month to three months.

## Who fixes it when the platform changes its API

- **Monitoring**: We check the connector against the live API every day and log every failed call.
- **Versions**: We track the platform's changelog and move the connector to a new version before the old one is retired.
- **Alerts**: Lost or stuck orders page the on-call engineer, who fixes them under the SLA.

## Questions

### Does Toast have an open API?

Toast has a documented REST API at doc.toasttab.com, but access isn't open to anyone. You get it in one of four ways: as an approved integration partner, through a custom integration for a Toast customer, through read-only Standard API access, or through Analytics API access.

### How do we get Toast API access?

For read-only data, a location on Restaurant Management Suite Essentials or higher can create Standard API credentials in Toast Web. To write orders, labor or stock, you need a custom integration set up with Toast for your restaurants, or partner status. The partner route adds vetting, a signed agreement, a certification demo and an alpha and beta before general release.

### What can be integrated with Toast?

Orders can be read and written, along with labor and stock. Menus, restaurant configuration, kitchen and cash data are read-only. Sales reporting comes through the Analytics API. Loyalty and gift cards work the other way around: Toast calls an endpoint you host.

### How long does a Toast integration take?

Published agency estimates range from $3,000–8,000 and two to four weeks for a first connector (Cadence, May 8, 2026) to $25,000–70,000+ and six to ten weeks (Bolder Apps, 2026). The partner route adds Toast's own alpha at one restaurant and a beta at three to five locations. We fix the price per scope before the build.

### Do we need to become a Toast integration partner?

Not if you are a restaurant group connecting your own locations. A custom integration or Standard API access is enough. Partner status makes sense for a software company that wants to sell its product to many Toast restaurants.

### Does it work when franchisees run their own Toast accounts?

Yes, but each location has to grant access, and every API call carries that location's ID. Plan who asks each franchisee for access and how menus map across brands before the build starts.

## Get a scope estimate for your Toast integration

Tell us which Toast locations you run, what else they need to talk to and what data you need back. An engineer will reply with the access route and how long it takes.

## Where this integration is used

- **[POS and delivery integrations](https://dev.family/foodtech/pos-integration)**
- **[Master menu management](https://dev.family/foodtech/menu-management)**
- **[Restaurant groups and franchises](https://dev.family/foodtech/multi-brand-franchise)**
- **[Square](https://dev.family/foodtech/integrations/square)**
- **[Lightspeed](https://dev.family/foodtech/integrations/lightspeed)**
- **[Olo](https://dev.family/foodtech/integrations/olo)**
- **[Deliverect](https://dev.family/foodtech/integrations/deliverect)**
- **[DoorDash Drive](https://dev.family/foodtech/integrations/doordash-drive)**

---

Last updated: 2026-11-10
Page: https://dev.family/foodtech/integrations/toast
Contact: https://dev.family/project-evaluation