Skip to main content
Changes to the Developer API surface — new endpoints, new event types, and behavior changes — are recorded here. The endpoint reference always reflects the current state.
​
Delivery addresses, order catch-up, and denser webhook retries
  • Delivery addresses — the order resource and the order.notification payload now carry delivery_address (street, unit, city, state, ZIP, and the customer’s delivery instructions in notes). It is null for pickup orders and for delivery orders with no stored address. See Receiving orders.
  • Order catch-up — GET /v1/orders accepts since, starting_after, and limit. With since, results drain oldest first from an exclusive checkpoint so you can page through a backlog after downtime. See Lists.
  • Order resend — POST /v1/orders/{orderId}/resend publishes a fresh order.notification for one live order that missed its webhook, without changing order state. Requires webhooks:write; terminal orders can’t be resent.
  • Denser webhook retries — a failed delivery is now retried up to 9 times (was 6), with the early attempts inside the six-minute POS decision window. See Retries and auto-disable.
​
Developer API launch
The Maple Developer API is available for POS and platform partners.
  • Authentication — API keys (mpk_test_… for the sandbox, mpk_live_… for production) with scoped access.
  • Locations and connections — list granted locations and connect as a location’s order receiver.
  • Orders — receive order.notification, read the full order, and decide it with accept / deny / ready / complete / cancel / status. Optional pre-validation.
  • Menu — publish a location’s full menu as one JSON document keyed by your own external IDs, and read it back.
  • Webhooks — subscribe to event types, verify HMAC-signed deliveries, and replay from the event ledger.