A8gent
All articles

Industry

Toast API Access: What You Get, What It Costs, and How to Turn It On

A US Toast restaurant on Restaurant Management Essentials or higher can create its own read-only API credentials in Toast Web, with no developer application. Write access goes through your Toast rep. Here is the plan rule, the exact menu path, the scopes, the rate limits, and three automations it unlocks.

A8gentAutomation practiceNovember 17, 202610 min read

Short answer: Yes, a Toast restaurant can get its own API access. In the US it comes with Restaurant Management Essentials or higher, at no extra line item, and you create the credentials yourself in Toast Web. It is read-only: orders, menus, labor, stock and more, plus webhooks. Anything that writes back into Toast needs your account rep, and Toast does not publish what that costs.

Contents
  1. The Short Answer: Access by Plan
  2. What Standard API Access Can and Cannot Touch
  3. How to Turn It On: The Exact Steps
  4. Three Automations Read-Only Access Unlocks
  5. When Read-Only Is Not Enough: The Workaround and Its Risks
  6. Time to Build and Running Cost
  7. What Breaks
  8. Not Sure What Your Toast Account Allows?
  9. Sources
  10. FAQ

The Short Answer: Access by Plan

Toast has two very different doors. Standard API access is the one an owner can open alone: read-only credentials you create inside Toast Web. Write access or a custom integration is the other door, and Toast's support article says plainly that it "is arranged through your Toast account representative". Everything below was checked on Toast's own support site and developer guide on 17 November 2026.

Your Toast setupAPI accessWhat it costs (as published)
US, Restaurant Management EssentialsStandard API (read-only) and webhooksIncluded in the suite. No separate dollar figure is published.
US, Restaurant Management Pro or EnterpriseStandard API plus the Analytics APIIncluded in the suite. Prices are in Toast Shop or your Subscriptions page, not on the support site.
Location without Essentials or higherNone for that location. It shows as locked when you create credentials.Upgrade that location first.
Outside the US, or on an MSA contractStandard API, billed as its own subscriptionShown on invoices as "API Monthly Subscription" or, on older ones, "Partner Integration". No amount published.
Need to write data (create orders, change menus)Custom or partner integrationThrough your Toast rep. Not published.

The "Partner Integration" invoice line is not a fee for one partner. Toast says it "reflects general access to Toast's API, not a fee for any one integration". Older blog posts quote a per-location integration fee; we could not find it on a Toast page today, so ask Toast support to confirm any line item.

What Standard API Access Can and Cannot Touch

The scope list in Toast's developer guide is the real boundary. You pick scopes when you create the credentials, and every one of them ends in :read.

AreaCan you do it with Standard API access?Notes from Toast's docs
Read orders, including takeout and delivery guest detailsYesorders:read, guest.pi:read, delivery_info.address:read. Guest data is only provided for Takeout or Delivery orders, not in-store orders.
Read menusYes, menus v2 onlyCalling the menus v3 endpoints returns a 403.
Read labor, employees, cash management, stock, kitchen, restaurant configYesEach has its own read scope.
Get pushed events instead of pollingYesWebhook categories: menus, orders, packaging preferences, restaurant availability, online ordering schedule, stock.
Create or change anything (orders, menu items, 86 an item)No"Standard API access only supports GET requests."
SandboxNoListed as not included. You read live data from day one.
Analytics APIPro and Enterprise onlySeparate credentials and tier.

Rate limits. Toast's default is 20 requests per second and 10,000 per 15 minutes, per location when you send the restaurant header. Menus allow one request per second per location; bulk orders allow five, and Toast recommends the orders webhook over polling it. One restaurant will rarely notice. A 15-location group polling every minute will.

How to Turn It On: The Exact Steps

This takes about ten minutes if you have the right permission. From Toast's developer guide, checked 17 November 2026:

  1. Check the permission. You need the Manage Integrations permission (Toast numbers it 8.4) for every location you want. If the Manage credentials screen is missing, this is why. Ask whoever owns the Toast account to grant it.
  2. Check the subscription. Each location needs Restaurant Management Essentials or higher. Locations without it appear dimmed with a lock.
  3. Open Toast Web and go to Integrations > Toast API access > Manage credentials.
  4. Select the arrow next to Create new credentials, then Standard API.
  5. Name the credentials after the job, for example "Review requests", so you can revoke one without breaking the others.
  6. Pick only the scopes you need. A review-request flow needs orders:read and guest.pi:read, not labor or cash.
  7. Choose the locations, select Apply, then Confirm. Toast emails a confirmation listing each location and its GUID.
  8. Copy the Client ID, the API access URL and the secret into a password manager. When you rotate a secret, Toast shows the new one once.

You can hold up to 100 sets of Standard API credentials per management group. Webhooks are set up on the Manage webhooks page in the same area: + Add webhook, then the credentials, the event category and your URL. One subscription covers one event category, and you cannot change its credentials after saving.

For write access, email your Toast rep the exact action you need, such as "mark an item out of stock from our supplier feed". A specific request gets a clearer answer.

Three Automations Read-Only Access Unlocks

Read-only sounds limiting, but most useful restaurant automations read from the POS and act somewhere else.

1. Review requests after takeout and delivery. The orders webhook fires, your workflow waits a set time, and it sends a short message asking for a review. Guest contact details are only in takeout and delivery orders, which fits. Our post on restaurant review response automation covers what Google allows on the reply side.

2. Stock alerts to the kitchen manager. The stock webhook tells you when an item's quantity changes. A workflow posts to a group chat when a key item drops below a number you choose, before the dinner rush finds out the hard way.

3. A daily sales and labor digest. Each morning a workflow reads yesterday's orders and labor and sends one plain summary per location: sales, covers, labor hours, voids. No logging into Toast Web on a phone.

Worked example: the review-request flow

An illustrative two-location restaurant, about 60 takeout and delivery orders a day across both sites.

  • Trigger: Toast orders webhook, filtered to Takeout and Delivery.
  • Check: skip if the order was voided, or if the same phone number got a request in the last 30 days.
  • Wait: 90 minutes after the order closes.
  • Send: one text or email with the Google review link for that location.
  • Fallback: once a night, pull the day's orders through the API to catch any event that did not arrive. This is our practice, not a Toast rule.

That is 60 webhook events a day plus one nightly pull per location, nowhere near Toast's limits. The real cost is messaging. If you text guests, US carriers require registration first; see our A2P 10DLC guide.

When Read-Only Is Not Enough: The Workaround and Its Risks

If the job needs to write into Toast, you have three honest options:

  • Ask your rep for write access. This is the only route Toast names. Expect a conversation about the use case, and get the price and terms in writing before anything is built.
  • Use a Toast partner integration that already has write access. Toast's suite overview lists partner integrations from Essentials up. If a partner already does the write you need, that is usually cheaper than a custom build.
  • Write somewhere else. Many "write" jobs are really "tell a human". A stock alert that tells the manager to 86 the item in Toast takes two seconds of their time and needs no write access.

What we would not do: drive Toast Web with a browser bot that clicks buttons for you. It breaks when the screen changes, it sidesteps the access controls Toast built, and it runs on a staff login instead of scoped credentials. Read Toast's terms before anyone suggests it. HIPAA is not usually the issue for a restaurant, but guest phone numbers and addresses are still personal data your tools must protect.

Time to Build and Running Cost

Toast's side costs nothing extra if you are already on Essentials in the US. The money goes on the build and the tools around it. The figures below are market-typical ranges for small-business automation work in 2026, not a8gent prices. Get written quotes.

  • Access: about 10 minutes, $0 extra on Essentials in the US.
  • One read-only workflow (review requests or a digest): roughly $1,000 to $4,000 one-off and 1 to 2 weeks, driven by locations, channels and testing.
  • A write-back integration: unknown until Toast prices the access.
  • Running cost: roughly $0 to $50 a month to host the workflow tool, plus usage-based texts or emails.

Our automation build cost page explains the drivers, and AI automation cost covers the wider budget. If you would self-host, read the true cost of self-hosting n8n first.

What Breaks

  • A new location is not added to the credentials. The workflow keeps running and silently skips the new site. Add locations on the Edit credentials page when you open one.
  • A missed webhook. Your endpoint was down for an hour. Without the nightly pull, those guests never get asked.
  • Mostly dine-in trade. In-store orders carry no guest data, so a review flow built on Toast orders reaches few guests.
  • The creator leaves. Only active employees with the permission can create credentials. Make sure someone still owns them.
  • One location's subscription lapses. Its calls start failing with 403 errors.

For the wider restaurant picture, see AI automation for restaurants and catering enquiry automation.

Not Sure What Your Toast Account Allows?

Send us your Toast tier, how many locations you run, and the one job you want off your plate. In the free automation audit we tell you whether read-only access covers it, whether you need to talk to your Toast rep first, and what the build would involve. If it is worth doing, our automation services team can build it and hand it over with plain reports on what ran.

Sources

All checked on Toast's own sites on 17 November 2026.

FAQ

Does Toast have an API for restaurant owners?
Yes. Toast's Standard API access lets a restaurant create its own read-only credentials in Toast Web under Integrations > Toast API access > Manage credentials. In the US it is part of Restaurant Management Essentials or higher. You need the Manage Integrations permission for each location.
How much does Toast API access cost?
For US customers, Toast says Standard API access is included in Restaurant Management Essentials, so there is no separate published fee. Outside the US or on an MSA it is billed as its own subscription, but Toast does not publish the amount. Write access is priced through your account rep.
Can I write data back into Toast through the API?
Not with Standard API access. It supports GET requests only, and a POST returns a 403 error. Toast says write permissions or a custom integration are arranged through your Toast account representative.
Does Toast support webhooks?
Yes, for Standard API access users. You can subscribe to menus, orders, packaging preferences, restaurant availability, online ordering schedule and stock events. Each subscription covers one category and is set up on the Manage webhooks page in Toast Web.
What are Toast's API rate limits?
The default is 20 requests per second and 10,000 requests per 15 minutes, applied per location when you send the restaurant header. The menus endpoint allows one request per second per location, and bulk orders five per second per location.
Why does my Toast API call return a 403?
Toast lists four common reasons: you sent a POST, you called the menus v3 endpoints, your credentials do not include that restaurant, or the credentials are missing the scope that endpoint needs.

If this resonated

Module 02 is the long version of this post.

Eval set, refusal pattern, kill switch. Build it in a weekend.

All postsLast verified 2026-11-17

Done for you

Want this built for your business?

Tell us the workflow. We scope, build, and ship the agent with guardrails and the numbers to prove it worked. The scoping call is free.

Free scoping call. You own the code.

Request a scoping call