Resources
Changelog
Notable changes to the Maple Developer API.
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.
November 2026
Webhook scopes removed
- Breaking: the scopes
webhooks:readandwebhooks:writeare gone. Managing your app’s webhook subscriptions (create, list, get, update, delete, send a test) needs only a valid credential for the app in that mode. To create or update a subscription, the credential must hold the read scope of each event type’s resource:orders:readfororder.*,catalog:readforcatalog.sync.*,locations:readforstore.*. A missing scope answers403with codeinsufficient_scope. An update is checked against every event type the subscription will hold afterward. See Subscribing. - The event ledger (
GET /v1/webhook_events,GET /v1/webhook_events/{eventId},POST /v1/webhook_events/{eventId}/replay) now shows only events whose type your credential may read. Any other event answers404. POST /v1/orders/{orderId}/resendnow needsorders:writeinstead ofwebhooks:write. Your app must still be the restaurant’s order receiver.- Keys and OAuth clients that held the old scopes simply lose those two names. A request that asks for them (a new key, an OAuth token scope, a listing draft) is refused like any unknown scope. Check that each key still holds the read scopes of the events it subscribes to.
November 2026
Read orders, catalog and delivery zones with a grant
- An app with a grant for a location and the read scope can now read the location’s orders (
GET /v1/orders,GET /v1/orders/{orderId},orders:read), catalog (GET /v1/locations/{locationId}/catalog,catalog:read) and delivery zones (list, get and the address check,delivery_zones:read) without being its order receiver. Publishing the catalog, creating, updating and deleting delivery zones, order decisions and resends still need the active connection. Order webhooks still go only to the order receiver.
November 2026
Open sign-up and one host for test and live
- Sign-up is open. Anyone can go to developers.maple.inc, create an organization and an app, make a test key, create a test restaurant and place a test order.
- One host,
https://api.maple.inc/v1, serves test and live keys. Ampk_test_…key reaches test restaurants only; ampk_live_…key reaches real restaurants only. The separate sandbox host is gone. See Test and live modes. - The Postman environments for staging and production are now one file,
maple-developer-api.postman_environment.json. See Postman. - Bookings and the waitlist are no longer in the public docs, the API reference or the Postman collection. The entries below stay as history.
- Breaking: the menu surface is now the catalog. The scopes
menus:readandmenus:writeare nowcatalog:readandcatalog:write,/v1/locations/{locationId}/menuis now/v1/locations/{locationId}/catalog, and themenu.sync.completedandmenu.sync.failedevents are nowcatalog.sync.completedandcatalog.sync.failed. Maple moved existing keys and apps to the new scope names, so only the route path and event names need a code change. See Publish your catalog.
November 2026
Rate limits on every route
- Every authenticated request now counts against rate limits per location and per app, in each environment: in live, 120 requests a minute per location and 6,000 per app; in test, 60 and 300. A request counts per location when its path names one (
/locations/{locationId}/...); every request counts per app. Order, menu, location, delivery zone, webhook and connection routes had no limit before; bookings and waitlist calls had their own budget of 300 a minute, which is gone. Availability searches keep a budget of 60 a minute, now per location. Over a budget the API answers429withretry_afterand aRetry-Afterheader, as before. Maple can raise an app’s live limits. See Rate limits.
October 2026
OpenTable refusals use the native codes
- At OpenTable-managed locations, a refusal OpenTable gives a reason for now answers with the code a Maple-native location gives, in Maple’s words, instead of
422 provider_rejectedwith OpenTable’s text. A time too soon answers422 outside_booking_window(details.reason: inside_min_lead); a reservation that has started or is about to409 not_changeable/409 not_cancellable(details.reason: outside_policy_window); a time that needs a card422 payment_instrument_required. Other refusals stayprovider_rejected. - OpenTable takes nothing under 15 minutes away, so availability at OpenTable-managed locations starts just over 15 minutes from now: a search that starts sooner returns the slots from then on, and one that ends sooner answers
422 outside_booking_window(details.reason: inside_min_lead).
October 2026
Change only a booking's note
POST /v1/bookings/{bookingId}/changetakesnoteswithoutslot_tokento change only the guest’s note: the booking keeps its time, party size and table, so no quote is needed. Sending neither field answers400 change_required.
September 2026
Experiences
- Availability lists experiences (prix fixe, tastings, ticketed seatings) where the location offers them, alongside standard slots in start order. Each
booking_slothas anexperience(id,name,description,prepayment_required),nullfor a standard reservation.experience_idnarrows a search to one experience. Offered at OpenTable locations;booking_profile.capabilities.experiencessays whether a location offers them. - An experience slot books through the usual hold and booking flow, and the
Bookingresource (and its webhook payloads) carriesexperience(id,name),nullfor a standard reservation. A change keeps the experience: a slot for a different experience, or between an experience and a standard table, answers422 capability_unsupported. - Holding a slot whose experience asks for payment up front answers
422 payment_instrument_required: Maple can’t take payment yet.
September 2026
Seated reservations at OpenTable locations
- At OpenTable-managed locations, changing or cancelling a reservation the party is already seated at, or one that is over, now answers
409 not_changeableor409 not_cancellable(reasonin_serviceorterminal_state) before Maple calls OpenTable, as it already did at Maple-native locations.
September 2026
Venues control guest texts
- Restaurant managers can now turn Maple’s guest texts off for their location. Where they have,
POST /v1/waitlist_entries/{entryId}/notifyanswers422 guest_messaging_unavailable, as it already did where guest texts aren’t rolled out. Seat or remove the party instead. - Managers can also turn Maple bookings on themselves once a configuration is published, so
booking_profile.enabledcan change without Maple’s involvement. Keep checking it before offering availability.
September 2026
Configuration revisions
- The booking configuration carries a
revision. Publish withexpected_revisionto get409 stale_configurationinstead of overwriting a configuration a restaurant manager edited in the Maple dashboard since your read;nullexpects no configuration yet. Publishing without it still replaces the configuration unconditionally.
September 2026
Every seating area is bookable
- Maple-native availability now seats parties in every configured area, not only the first: it tries the first area, then the others in
poolIdorder, and books the first with a free table or combination that fits. A party only another area can seat (a large table on the patio) is now offered. Party-size bounds span all areas.
September 2026
Find bookings by phone or confirmation code
GET /v1/bookingstakesphoneandconfirmation_codeto find the booking a guest is asking about. Both requirelocation_id; the phone is normalized first. Without a window a lookup matches bookings at any time, at native and provider-managed locations alike. A lookup withoutlocation_idanswers400 location_required.
September 2026
Booking blackout dates
GET /v1/locations/{locationId}/booking_profilereturns the location’sblackout_dates: windows when it takes no reservations.PUT /v1/locations/{locationId}/booking_blackoutsreplaces the list underbookings:configure, at native and provider-managed locations. Send the profile’sblackout_dates_revisionasexpected_revisionto get409 stale_blackout_datesinstead of overwriting the venue’s newer edits. Invalid ranges answer400 invalid_blackout_dates.
September 2026
Validation errors and the feedback hint
- A request whose path parameters, query, headers or body fail validation now answers
400with aDeveloperApiBadRequestbody (code: "invalid_request") naming the field, where it used to answer with an empty body. - Every error body carries a
feedbackline pointing toPOST /v1/feedback. See Errors.
September 2026
Feedback
POST /v1/feedbackreports a bug, a missing capability, wrong docs, or an unclear error, citing the ids of the requests involved. Onlykindandsummaryare required. An id Maple cannot match to your recent requests is kept as sent rather than refused. Any credential may send it; no scope is required. Its contract will not break: fields may be added, never removed or made required. See Feedback.
September 2026
Walk-ins and venue-side cancellation
POST /v1/locations/{locationId}/walk_insseats an arriving party at the earliest table that fits now and returns the seated booking, retry-safe under an app-scopedidempotency_key.POST /v1/bookings/{id}/venue_cancelcancels on the venue’s behalf (cancelled_by_venue), outside the guest’s cancellation window.- Both require
bookings:manageand are available at Maple-native locations. The API reference now lists the waitlist under its own section.
September 2026
Waitlist
- Read a native location’s walk-in queue and quote waits under
bookings:read. - Add parties with an app-scoped
idempotency_key, and cancel them for the guest, underbookings:write. - Notify, seat, and remove parties, and open or close the waitlist, under
bookings:manage. Maple sends every guest text; seating creates a walk-in booking. - Five waitlist webhook types (
waitlist_entry.created,.notified,.seated,.removed,.expired) carrying the entry’s latest state.
September 2026
Delivery zones
- Delivery zone CRUD for connected locations — list, create, get, update, and delete zones under
delivery_zones:read/delivery_zones:write, scoped to your app’s active connection. POST /v1/locations/{locationId}/delivery_zones/checkreports whether a coordinate is deliverable and returns the matching zone and fee. See Manage delivery zones.
September 2026
Bookings — per-location rollout
- Booking profile, bounded availability search, holds, and booking list/get/create/change/cancel.
- Venue actions under
bookings:manage, with version checks and app-attributed audit records. - Native configuration publish/read under
bookings:configure, preserving existing menus. - On-demand live floor, eight booking webhook types, and optional booking sandbox provisioning.
- App-owned native/provider holds, atomic ten-hold quotas per app/location, and separate booking request/search throttles with
Retry-After. - Durable provider-write claims, version reservations, stable request identities, and reconciliation after uncertain writes or mirror failures.
August 2026
Delivery addresses, order catch-up, and denser webhook retries
- Delivery addresses — the order resource and the
order.notificationpayload now carrydelivery_address(street, unit, city, state, ZIP, and the customer’s delivery instructions innotes). It isnullfor pickup orders and for delivery orders with no stored address. See Receiving orders. - Order catch-up —
GET /v1/ordersacceptssince,starting_after, andlimit. Withsince, 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}/resendpublishes a freshorder.notificationfor one live order that missed its webhook, without changing order state. Requireswebhooks: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.
August 2026
Customer phone and scheduled orders
- Scheduled orders — the order resource and the
order.notificationpayload now carryscheduled_for: the requested ready time as an ISO 8601 UTC timestamp, ornullfor an order wanted as soon as possible. - Customer phone —
customer.phone(E.164, ornull) andcustomer.phone_last_fourare now included on orders and inorder.notification. See Receiving orders.
June 2026
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.