Connect Toast POS

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: restaurants food. How Toast gives access: The vendor charges extra for API access or a higher plan. Check your plan before you start. What it costs you: Toast says standard API access is bought from the Toast Shop; the price was not read in the public docs.

Part 1. Get your key from Toast

Do this on your computer, in a new browser tab, signed in to Toast.

  1. Sign in to Toast Web as the restaurant owner or manager.
  2. Open the Toast Shop and look for Toast API access (standard API access is sold there).
  3. Buy or request standard API access and, when asked, say you need read-only access to Orders so your phone assistant can report order status.
  4. If Toast asks for an integration partner agreement, contact your Toast account manager or Toast support and ask for read-only Orders API credentials for your restaurant.
  5. When Toast confirms, copy the client ID and client secret it gives you.
  6. Copy your restaurant GUID (shown with your API credentials or in Toast Web under restaurant identifiers).
  7. Paste the three values into Speakvora and tick only Orders: read.

WARNING: If Toast asks which permissions to give, tick only the read-only ones: orders: read (orders:read scope). 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

  1. Open your agent's dashboard (the page you open from the Start Speakvora Agent file).
  2. 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.
  3. Step 1: press Connect (1)

  4. Under Your apps type Toast in the box that says Find an app (1), or scroll down the list.
  5. Step 2: the Find an app box (1)

  6. Press Toast POS. 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.)
  7. Step 3: an app's card. The Full Guide button (1) opens this page.

Part 3. Paste it in

3 boxes to fill in. Click inside a box, press Command + V on a Mac or Ctrl + V on Windows, then move to the next:

  1. API client ID. Handed over by Toast after your API access is approved.
  2. API client secret (secret: it stays on this computer and is never shown again, only the last few characters). Issued together with the client ID. Keep it private.
  3. Restaurant GUID. The ID of your individual restaurant location (not a restaurant group), sent as the Toast-Restaurant-External-ID header.
  4. Part 3: each numbered box is one thing to paste. These are made-up examples.

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

  1. Press the orange Save and test button.
  2. 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.
  3. Part 4: the green message under the buttons means it worked (1)

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 uses a client ID and secret that are exchanged for a short-lived bearer token, and its authentication page could not be read from the public docs, so the token exchange is not confirmed. The single-order read is documented as GET /orders/v2/orders/{guid} with a bearer token and a Toast-Restaurant-External-ID header; the status fields are approvalStatus, paymentStatus and voided, and displayNumber is the number staff see. Toast orders are looked up by GUID, not by the display number, so test and order calls are left out until confirmed against a live account.
  • Still stuck? Press Connect, then Download report, and email it to support. It never contains keys or customer messages.

If your plan has no API

  • Ask Toast support to enable an order-status email or text feature instead.
  • Staff read the order status aloud from the Toast screen.

Toast's own instructions: https://doc.toasttab.com/

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 uses a client ID and secret that are exchanged for a short-lived bearer token, and its authentication page could not be read from the public docs, so the token exchange is not confirmed. The single-order read is documented as GET /orders/v2/orders/{guid} with a bearer token and a Toast-Restaurant-External-ID header; the status fields are approvalStatus, paymentStatus and voided, and displayNumber is the number staff see. Toast orders are looked up by GUID, not by the display number, so test and order calls are left out until confirmed against a live account.

What if this happens: Still stuck??

Press Connect, then Download report, and email it to support. It never contains keys or customer messages.