Authenticated restaurant API access
The documented restaurant API supports scoped operations such as menu, orders and reservations using restaurant credentials. It is separate from public product-information endpoints.
Confirm this capability's plan and scope before purchase.
- Workflow and demonstration
- Review the actual API documentation, name the required operation and test permissions/errors with a safe test restaurant before integration.
- Prerequisites
- An authorized key, tenant scope and eligible access are required. Confirm the current API entitlement before purchase; the public plan documentation does not resolve it consistently.
- Connectivity and offline behavior
- Configuration and shared records need internet. Confirm the exact desktop screen separately.
- Limitations
- Unauthenticated product facts do not expose restaurant records. No undocumented webhook, accounting connector, rate/SLA or automatic marketplace import is promised.