← Back to all docs

CrunchTime API

CrunchTime is an AI-powered restaurant operations platform that unifies inventory, labor, kitchen, and task execution across multi-unit brands. An unofficial API lets you programmatically pull inventory items, recipes, food cost, labor schedules, sales forecasts, vendors, and audit results—and push updates like purchase orders, schedules, and task completions back into CrunchTime.

By Alex KlarfeldMay 30, 2026
CrunchTime API

What is CrunchTime?

CrunchTime is an AI-powered restaurant operations management suite that unifies inventory, labor, kitchen, and task execution across multi-unit restaurant brands. Operators use CrunchTime to control food cost, forecast demand, automate purchasing, schedule and optimize labor, run kitchen display and guest-management workflows, and enforce food-safety and brand-standard audits across tens of thousands of locations.

Core product areas include:

  • Inventory Management (food cost control, AI forecasting, purchasing automation)
  • Labor & Scheduling (staffing optimization, schedule management, labor-law compliance)
  • Operations Execution / Zenput (task management, audits, temperature monitoring, food prep labeling)
  • Kitchen Management (Kitchen Display System for order flow and demand management)
  • Guest Management (host stand operations)
  • Operational Intelligence (Crunchtime Insights, Data Streaming) and Learning & Development (employee training and compliance)

Common data entities:

  • Items, Recipes, Counts, Cost of Goods Sold, Waste
  • Vendors, Purchase Orders, Receipts, Transfers, Invoices
  • Sales Forecasts, POS Sales, Daypart Volumes
  • Employees, Positions, Schedules, Shifts, Labor Hours
  • Locations, Sites, Application Users, Reference Data
  • Audits, Tasks, Temperature Logs, Training Records

The CrunchTime Integration Challenge

Restaurant operators run mission-critical inventory and labor workloads on CrunchTime daily, but turning portal- and config-driven workflows into reliable API automation is non-trivial:

  • Token gating and admin enablement: API tokens must be provisioned per environment through Enterprise Manager, and developers contact CrunchTime Support to request access
  • Multi-service spread: Inventory & Labor, Ops Execution/Zenput, Learning & Development, and Cruise each expose their own service surfaces, IDs, and conventions
  • Strict referential matching: Updates require location, position, and reference names to match existing entries exactly—the API will not auto-create reference records
  • Site- and tenant-specific hosts: Calls require a sitename and the net-chef.com host, plus a dedicated application user, varying per brand deployment
  • Paged and filtered retrieval: getAll requires filter parameters while getByPage drives bulk pulls, and large multi-unit datasets must be paged carefully to avoid load
  • Mixed API and flat-file paths: Some data flows still move via flat files rather than real-time APIs, requiring you to bridge both patterns
  • Cross-system reconciliation: POS, accounting, payroll, and supplier integrations all feed CrunchTime, so entity IDs must be reconciled across upstream systems

How Supergood Creates CrunchTime APIs

Supergood reverse-engineers authenticated CrunchTime sessions and its Inventory & Labor, Ops Execution, and Cruise service surfaces to deliver a resilient, normalized API layer for your CrunchTime tenant—across inventory, labor, sales forecasting, and audits.

  • Handles token, sitename, and application-user authentication securely across Test and Production environments
  • Maintains session continuity with automated token refresh and change detection
  • Normalizes responses across Inventory, Vendors, Sales, Labor, and Ops Execution so you integrate once and rely on consistent objects
  • Resolves referential matching for locations, positions, and items so writes land cleanly without manual reference setup

Use CrunchTime with AI agents: CrunchTime MCP Server →

Getting Started

  • Schedule Integration Assessment

Book a 30-minute session to confirm your modules, locations, and authentication model.

  • Supergood Generates and Validates Your API

We deliver a production-ready CrunchTime adapter tailored to your tenant, sites, and entitlements.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as CrunchTime evolves.

crunchtime

API Endpoints

Authentication

POST/authenticate

Authenticate to a CrunchTime tenant using API token, sitename, and application user credentials, and obtain a session for downstream calls.

Inventory

GET/items

List inventory items, recipes, counts, and cost-of-goods data across locations with filters for category, vendor, and date range.

Purchasing

GET/vendors

Retrieve vendors, supplier catalogs, and pricing used for purchasing and order-guide automation.

Purchasing

POST/create_purchase_order

Submit a purchase order against a vendor and location with line items, quantities, and delivery dates.

Sales

GET/sales_forecasts

Pull AI-driven sales forecasts and POS sales by location and daypart to drive inventory and labor planning.

Labor

GET/schedules

Retrieve labor schedules, shifts, positions, and worked hours for staffing optimization and payroll export.

Use Cases

Sync inventory and food cost into your data warehouse

- Pull items, recipes, counts, and cost-of-goods data across all locations into a single warehouse - Stream waste, variance, and transfer events to downstream BI and finance tools - Reconcile vendor invoices and receipts against purchase orders for unified cost reporting

Automate purchasing and order guides

- Generate purchase orders from forecast-driven par levels and push them to vendors - Pull supplier catalogs and pricing to keep order guides current - Trigger receiving and transfer workflows without portal clicks

Align labor schedules with demand forecasts

- Pull AI sales forecasts and daypart volumes to drive optimized labor schedules - Push schedules and shift changes back into CrunchTime and downstream payroll - Surface labor-law compliance and overtime exposure to managers in real time

Centralize audits and food-safety compliance

- Pull task completions, audit results, and temperature logs from Ops Execution / Zenput - Route failed audits and out-of-range temperatures to corrective-action workflows - Aggregate brand-standard and training compliance across the location network

Technical Specifications

Authentication

API token plus sitename, application user ID, and password handled in a managed session across Test and Production

Connectivity

Authenticated CrunchTime web services (net-chef.com) plus Inventory & Labor, Ops Execution, and Cruise service surfaces

Response format

Normalized JSON across Inventory, Purchasing, Sales, Labor, and Ops Execution objects

Rate limits

Adaptive throttling tuned to your tenant, favoring the test environment for development to avoid production load

Session management

Automatic token refresh, environment-aware credentials, and credential rotation

Data freshness

Near real-time pulls for inventory, sales, and labor with optional scheduled batch syncs

Security

Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging

Webhooks

Event-style callbacks for purchase orders, receipts, schedule changes, and audit/task completions

Latency

Sub-second reads on cached entities; multi-second writes when posting purchase orders and schedules

Throughput

Horizontally scaled workers sized to multi-unit volume across tens of thousands of locations

Reliability

Retry, backoff, and idempotency keys for purchase orders, receipts, and schedule writes

Adaptation

Continuous monitoring of CrunchTime releases, service changes, and tenant-specific configuration drift

Frequently asked questions

Yes. Supergood normalizes data across CrunchTime's Inventory & Labor services as well as Ops Execution / Zenput and Cruise, so you can integrate items, vendors, forecasts, schedules, and audits through one consistent API surface.

Supergood works with your existing CrunchTime entitlements. We help provision and manage the API token, sitename, and dedicated application user that CrunchTime requires, and handle environment-aware credentials for Test and Production.

CrunchTime requires reference names to match existing entries exactly and will not auto-create them. Supergood resolves locations, positions, and items against your tenant so writes land cleanly without manual reference setup.

Yes. CrunchTime's AI sales forecasts and POS sales are exposed through the normalized API so you can feed par levels, purchasing, and labor scheduling from the same demand signal.

Yes. The adapter is sized for multi-unit brands operating across tens of thousands of locations, with paging and adaptive throttling tuned to keep large pulls reliable.

Ready to get a real API?