Connect your Toast account to Patch

Who does what

You do	Your Patch onboarding rep does
Have a Toast admin with Manage Integrations create Standard API credentials	Match Patch timezone to your restaurant
Enter Client ID and Client Secret in Patch	Map each restaurant to the right Patch account (multi-location)
Tell your rep when it says Authenticated	Activating the integration and starting the first sync
Optional: set up order webhooks in Toast using the URL from Patch Settings	Historical backfill / Last Pull Time

You don’t need a Patch partner app key. Patch connects the rest for you.

Before you start

You’ll need:

A Toast admin who can Manage Integrations.
A Standard API client ID and client secret for your restaurant(s), with access to:
- Orders
- Guest details (name, email, phone on checks)
- Restaurants list
- Menus
Your restaurant’s timezone in Toast (your Patch account should match it).

Important: Patch only creates contacts and orders when Toast has a guest email or phone on the check. Most dine-in checks don’t — takeout, delivery, and curbside usually do.

Step 1: Create Toast API credentials

In Toast, generate Standard API access credentials for the restaurant(s) you want connected. Ask Toast support or your Toast admin if you’re unsure where Manage Integrations lives for your account.

Share the Client ID and Client Secret with whoever will enter them in Patch (keep them private — treat them like a password).

Step 2: Enter the credentials in Patch

In Patch, go to Settings → Toast.
Enter the Toast Client ID and Client Secret.
Click Save & Verify.

You should see Authenticated. That’s your main part done — let your onboarding rep know.

If it doesn’t verify:

Confirm the same credentials work in Toast’s API access area.
Confirm guest / order / restaurant / menu access was included when the credentials were created.
If you see a timezone warning, leave it for your rep — they’ll match Patch to your Toast restaurant timezone.

Multi-location brands: your rep will tell you whether credentials go on the parent account (children can inherit). See Multi-location restaurants.

Optional: real time order updates (webhooks)

Patch syncs Toast on a schedule (about every 6 hours). For nearer-real-time order updates:

Open Settings → Toast and copy the Callback URL from the Webhooks card.
In Toast Web, subscribe order webhooks to that URL (Integrations → API access → Webhooks).
Paste the signing secret into Webhook Secret in Patch and save.

Until the secret is saved, webhook deliveries won’t update Patch. Your onboarding rep can walk you through this.

What happens next

Your rep activates the integration, assigns restaurants to the right Patch accounts if you have more than one location, and starts the first sync. A historical backfill can take a while depending on how much history you’re pulling.

Once you’re live:

Patch syncs on a schedule, about every 6 hours.
Order updates can arrive sooner when webhooks are set up.
There is no “pull this one guest from Toast” button — guests update when their next identifiable order syncs.

What syncs

Data	Notes
Contacts	From order guest info (email or phone required)
Orders	Closed checks with guest identity → Order Finished; refunds when applicable
Products	Menu items so order line items link to real products
Discount codes on orders	Codes applied on the check — Patch cannot create Toast promos

Toast does not send marketing opt-in to Patch. Consent for email and SMS is managed in Patch.

Your checklist

Toast Standard API Client ID / Secret created
Entered in Settings → Toast
Status shows Authenticated
Onboarding rep notified
Spot-check a few takeout/delivery guests in Patch after the first sync