Beta

Toast POS Restaurant Analytics

Restaurant intelligence beyond the POS terminal

Get Started API Docs

30sRefresh Rate

~40KData Points/Day

<100msNormalization

9API Fields

How It Works

Toast to AI in three steps

The Problem

Toast records every order and cover, but restaurant operators can't correlate dining room occupancy with kitchen throughput. The gap between POS data and spatial data costs money every shift.

The Solution

Order and cover tracking with table turn analytics
Revenue per seat hour and menu item performance
Kitchen throughput and prep time correlation
Multi-location restaurant group dashboards
Real-time dining room occupancy and waitlist optimization

Data Explorer

What Data You Get from Toast

Every field below is normalized into the GuestNetworks canonical schema and available via REST API and MCP tools.

Field Name ↑	Type	Description	Example
checks	array	Individual checks on the order	[{"amount": 43.75}]
closedDate	string	When the order was closed	2024-03-22T19:45:00Z
guid	string	Unique order identifier	ord_abc123def456
numberOfGuests	number	Cover count	4
openedDate	string	When the order was opened	2024-03-22T18:30:00Z
selections	array	Menu items ordered	[{"name": "Wagyu Burger"}]
server.guid	string	Server employee identifier	emp_srv_001
table.name	string	Table assignment	Table 14
totalAmount	number	Total order amount in dollars	87.50

Live Preview

This is what your AI agent sees

Every Toast event is normalized into this canonical JSON structure. One schema, any connector.

gn_canonical_event.json

{
  "event_type": "transaction",
  "connector": "toast",
  "venue_id": "ven_r3s7k2",
  "timestamp": "2024-03-22T19:45:00.000Z",
  "data": {
    "order_id": "ord_abc123def456",
    "amount": 87.5,
    "covers": 4,
    "table": "Table 14",
    "server": "emp_srv_001",
    "items": [
      {
        "name": "Wagyu Burger",
        "quantity": 2
      },
      {
        "name": "Caesar Salad",
        "quantity": 1
      },
      {
        "name": "Craft IPA",
        "quantity": 3
      }
    ],
    "turn_time_minutes": 75
  },
  "metadata": {
    "normalized_at": "2024-03-22T19:45:00.015Z",
    "schema_version": "1.0"
  }
}

Data Types

What You Get

Orderscoverstable turnsrevenue per seatmenu analytics

Visualizations

Built-in Chart Types

Every integration unlocks these dashboard visualizations. No configuration needed.

Revenue by Daypart

Revenue trends segmented by lunch, dinner, and late-night

Table Turn Funnel

From seating to close, tracking turn time optimization

Menu Category Mix

Revenue breakdown by food, beverage, and alcohol categories

Revenue per Seat Hour

Revenue efficiency correlated with dining room occupancy

Quick Start

Get your Toast data in 60 seconds

Four steps from zero to live data. Your credentials are encrypted with AES-256-GCM at rest.

Create a Toast API partner app

Create a GuestNetworks account

Register Toast integration

POST your Toast client credentials and restaurant GUID.

curl -X POST https://api.guestnetworks.com/api/venues/:id/integrations \
  -d '{"connector_type": "toast", "config": {"client_id": "...", "client_secret": "...", "restaurant_guid": "..."}}'