Connect Toast
A step-by-step guide with pictures, from the Speakvora agent's own Connect tab.
Short answer: This connects your own Toast account to your Speakvora agent. Then a customer can text where is order 1234 and get the answer in seconds, and the agent can send status and tracking texts. The agent only reads. It can never create, change or delete anything in Toast. Only the status word and the order number are ever.
Every key, number and name in the pictures is a made-up example. Nothing here asks you to share a real key with anyone but the app on your own computer.
This connects your own Toast account to your Speakvora agent. Then a customer can text *where is order 1234* and get the answer in seconds, and the agent can send status and tracking texts. The agent only reads. It can never create, change or delete anything in Toast. Only the status word and the order number are ever texted back, never names, prices, items or addresses.
TIP: You need about 15 minutes, a computer, and the sign-in for your Toast account (the owner or a manager). You can't break anything: if a step does not work, nothing has changed and you can just try again. The keys and screens below are made-up examples.
NOTE: This guide was written from Toast's public developer documentation (a few details could not be confirmed) and has not been tried yet on a live Toast account. If a screen looks different from what is described, press Connect, then Download report, and send it to support. We fix it for everyone.
Who this is for: bars food trucks. How Toast gives access: You create the key yourself in your own account; no approval is needed. What it costs you: Toast's docs state no separate price for API credentials; each location needs an active Toast Restaurant Management Suite Essentials or higher subscription.
Part 1. Get your key from Toast
Do this on your computer, in a new browser tab, signed in to Toast.
- Sign in to Toast Web as a manager whose role has the Manage Integrations permission.
- Open [[Integrations > Toast API access > Manage credentials]].
- Press the down arrow beside Create new credentials and choose Standard API.
- Type a name such as Speakvora for the credentials.
- Tick only the read scopes for orders, and choose your location (read-only access).
- Press Confirm, then copy the API Access URL, Client ID and Client secret from the credentials list.
- Find your Restaurant GUID in Toast's confirmation email for the new credentials.
- Paste the four values into Speakvora.
WARNING: If Toast asks which permissions to give, tick only the read-only ones: Standard API credentials with an orders read scope for your location (tick only read scopes). Never give write or admin access.
TIP: To copy the key, click inside the box that shows it, press Command + C on a Mac or Ctrl + C on Windows (or right-click and choose Copy). Nothing will look different. It is now in your clipboard, ready to paste. Keep it private: anyone who has it can read your orders.
Part 2. Open the Connect tab in your agent
- Open your agent's dashboard (the page you open from the Start Speakvora Agent file).
- Press Connect in the menu. On a phone the menu is the bar along the top; slide it sideways if you do not see Connect.
- Under Your apps type Toast in the box that says Find an app (1), or scroll down the list.
- Press Toast. A card slides up. (If you only see apps for your own kind of business, that is on purpose: your agent only shows the systems that make sense for it.)



Part 3. Paste it in
4 boxes to fill in. Click inside a box, press Command + V on a Mac or Ctrl + V on Windows, then move to the next:
- API access URL. The API Access URL copied from Toast Web, Integrations > Toast API access > Manage credentials. Enter only the host name.
- Client ID. Shown on the Manage credentials page for your Standard API credentials.
- Client secret (secret: it stays on this computer and is never shown again, only the last few characters). The secret for the same credentials. Toast shows a new secret when you rotate it, so copy it somewhere safe.
- Restaurant GUID. The location GUID listed in Toast's confirmation email for your credentials; Toast also calls it Toast-Restaurant-External-ID.

TIP: Pasted by mistake into the wrong box? Click the box, press Command + A (Ctrl + A on Windows) to select all, then paste again.
Part 4. Test it
- Press the orange Save and test button.
- Toast has no safe read-only check we can run, so nothing is called. The connection is used for real the first time a customer asks about an order, and any problem shows in Activity.

YOU SHOULD SEE: green words starting with Connected. (here: *Saved* and the sentence about the first customer)
WARNING: Red words mean it did not work yet. Read them, then see If something is wrong below. Nothing bad happened.
What happens next
- A customer texts something like where is order 1234. The agent answers *Your order 1234 is preparing.* (the status word from Toast), or *I could not find that order. A team member will check and reply.*
- Each person can ask five times an hour. If Toast is down, the conversation carries on and the problem is written to Activity.
- Mode: the agent asks Toast when a customer asks.
If something is wrong
- It says the key was refused (401 or 403): copy the key again from Toast. Make sure there is no space before or after it, and that it is a live key for the right shop or location.
- It cannot find an order (404): the number is not in Toast, or Toast uses a longer number than the one on the receipt.
- It says too many requests (429): wait a minute and press Save and test again.
- Toast says you need a plan or approval: Toast's API does not accept a pasted key. You post the Client ID and secret (userAccessType TOAST_MACHINE_CLIENT) to /authentication/v1/authentication/login to get a short-lived bearer token, then call GET /orders/v2/orders/{guid} with headers Authorization: Bearer and Toast-Restaurant-External-ID. That token exchange and the header cannot be expressed in this spec format, and the order endpoint looks up by Toast order GUID, not the short order number guests see (displayNumber), so no test or order call is included. Docs did not confirm that standard access is read-only; Toast says credentials are for read access to the chosen locations. Needs an employee with the Manage Integrations permission.
- Still stuck? Press Connect, then Download report, and email it to support. It never contains keys or customer messages.
Toast's own instructions: https://doc.toasttab.com/doc/devguide/apiOverview.html
All help guides · Every agent feature · AI receptionist by industry
Questions
What if this happens: It says the key was refused (401 or 403)?
copy the key again from Toast. Make sure there is no space before or after it, and that it is a live key for the right shop or location.
What if this happens: It cannot find an order (404)?
the number is not in Toast, or Toast uses a longer number than the one on the receipt.
What if this happens: It says too many requests (429)?
wait a minute and press Save and test again.
What if this happens: Toast says you need a plan or approval?
Toast's API does not accept a pasted key. You post the Client ID and secret (userAccessType TOAST_MACHINE_CLIENT) to /authentication/v1/authentication/login to get a short-lived bearer token, then call GET /orders/v2/orders/{guid} with headers Authorization: Bearer and Toast-Restaurant-External-ID. That token exchange and the header cannot be expressed in this spec format, and the order endpoint looks up by Toast order GUID, not the short order number guests see (displayNumber), so no test or order call is included. Docs did not confirm that standard access is read-only; Toast says credentials are for read access to the chosen locations. Needs an employee with the Manage Integrations permission.
What if this happens: Still stuck??
Press Connect, then Download report, and email it to support. It never contains keys or customer messages.