Skip to content

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.

Start integrating Explore endpoints
api.innovorder.fr
Restaurant network live flow
GET/v1/orders
Response DTO 200 OK
{
  "status": 200,
  "data": {
    "omnichannelOrders": [{
      "status": "PAID",
      "items": [ ... ],
      "totalPriceWithTaxIncluded": 1850,
      ...
    }]
  }
}

Choose your entry point

Get from intent to request.

START

Understand the contract

Authentication, API principles, security, and your first request.

REFERENCE

Find an endpoint

Requests, parameters, and production-shaped response examples.

RECIPES

Build a complete flow

Follow a real integration from sign-in to service.

Change feed

Latest updates.

View all
addedOct 21

Customers of "Mode enseignement" brands can read their daily payment cap and what is left of it for a day. Order creation (single and multi-orders) now refuses an overshoot with 400 payment_limit_reached before any payment.

addedOct 6

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.

changedOct 6

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.

addedSep 25

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.

addedSep 21

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.