Public API · Restaurant infrastructure
Make every restaurant system speak the same language.
Build ordering, payments, loyalty, catalog, and real-time events against one documented contract, from the first request to service at scale.
{
"status": 200,
"data": {
"omnichannelOrders": [{
"status": "PAID",
"items": [ ... ],
"totalPriceWithTaxIncluded": 1850,
...
}]
}
}Choose your entry point
Get from intent to request.
API surface
One contract, every service.
Change feed
Latest updates.
Guest App restaurant audiences restrict menus and service sessions by structured guest groups (including descendants) or exact legacy student classes. Authenticated restaurant lists are deployment-scoped; anonymous metadata omits restricted restaurants and audience rules.
Guest reservation availability now supports an optional bounded monthly calendar, with bookable local dates and maximum party sizes accounting for remaining seats. Existing daily queries are unchanged.
Eligible automatic Web discounts apply without a code at cart preview and are recalculated at order creation. Documented guest, service and product-tag eligibility, the expectedAt contract, and the preview discount labels, amounts, affected cart lines and final total.
Documented explicit customer metadata creation and version-checked updates/deletions, Text/JSON modes, access rules, reserved provenance protection and the optional customer provenance context. Clarified historical upsert/bulk-delete compatibility and HTTP/Pub/Sub rollout.
Guest App administrator domain onboarding: DNS instructions, background certificate activation, status, manual checks and pre-activation hostname correction.