All
Case 01
Scenario
Tenant uses Xero for accounting and wants daily order data pulled in.
Outcome with MISE AN PLACE
Xero integration polls /api/v1/orders?since=yesterday and reconciles. No manual export.
Feature
Connect MISE AN PLACE to everything else.
The bottom line
Your data is yours, programmatically. Plug it into anything that speaks REST or webhooks.
Included
Part of the Platform plan — no upgrade tier, no add-on cost.
Read your orders, products, customers via REST. Receive webhooks on every state change. Build whatever you need on top.
How to think about it
Most operators come to MISE AN PLACE because the workarounds stopped scaling. Here's what changes the day this feature is live.
Without it
With MISE AN PLACE
What's included
Built by people who've worked in scheduled-production food and spent too many evenings with spreadsheets. Each item below is there because we needed it ourselves.
REST API
GET /api/v1/orders, /api/v1/products. Bearer auth. JSON responses. Rate-limited at 600 req/min per key.
Outbound webhooks
Configure URLs to receive HMAC-signed JSON payloads on order.locked, order.delivered, quote.sent, etc.
Exponential backoff retries
Failed webhooks retry at 1m, 5m, 15m, 1h, 6h. Max 5 attempts before pending → failed.
Per-key scopes
Keys can read orders, products, customers — independently. No global admin keys exposed.
Public docs
Documentation lives at /docs/api with curl examples for every endpoint.
In the wild
Illustrative scenarios — not customer testimonials. These are the typical situations the feature was designed for.
All
Case 01
Scenario
Tenant uses Xero for accounting and wants daily order data pulled in.
Outcome with MISE AN PLACE
Xero integration polls /api/v1/orders?since=yesterday and reconciles. No manual export.
What you'll see
Sample webhook payload
{"event_type":"order.delivered","data":{"order_id":"...","order_number":"HP-00342"}}
Connected systems
Features aren't islands. Each connects to the rest of the platform.
14-day trial. No card. Live in under 30 minutes.