Skip to main content
The Maple Developer API connects your POS or platform to Maple. You receive orders the moment a customer places them, decide whether to accept them, publish the menus customers order from, and keep everything in sync through signed webhooks. There is no SDK to install, and there is no payment processing to build — Maple owns the entire customer payment lifecycle and hands you orders with totals already calculated. Most partners reach a working test integration in a few days.

Quickstart

Make your first authenticated call in a few minutes. Start here.

How Maple works

The mental model: apps, locations, connections, and who owns what.

​
Start with the job you’re doing

Receive and decide orders

Get order.notification webhooks and drive each order with accept, deny, ready, and complete calls.

Publish a menu

Send a location’s full menu as one JSON document keyed by your own stable IDs, and read it back.

Handle webhooks

Verify HMAC signatures, dedupe deliveries, and replay from the event ledger.

Browse every endpoint

Request and response schemas for auth, locations, connections, menu, orders, and webhooks.

​
What you never have to build

Restaurant integrations are usually painful because you inherit problems that aren’t yours. With Maple, you don’t:
  • No payment integration. Maple creates and owns the payment link. You never touch a card or carry PCI scope.
  • No pricing engine. Maple computes every customer-facing total. You read integer cents.
  • No polling. Orders are pushed to your webhook; a ledger and replay endpoints cover recovery.
  • No SDK required. It’s a REST API you can call from any language.
  • No guessing in production. You build against isolated test data first; live access is enabled once your integration is approved.

​
The shape of the API

Every request carries a Bearer credential. You develop against the sandbox and move to production by changing the base URL and credential — nothing else: 
# Sandbox — build and test here
curl https://api.staging.maple.inc/v1/me \
  -H "Authorization: Bearer mpk_test_..."
  • Two environments: the sandbox at https://api.staging.maple.inc/v1 for development, and production at https://api.maple.inc/v1. They’re fully isolated. See Environments.
  • API key auth: send your key (mpk_test_… / mpk_live_…) as a Bearer token. See Authentication.
  • Scoped access: your app holds only the permissions it needs (orders:read, menus:write, webhooks:write, and so on).
  • Predictable resources: opaque IDs, money as integer USD cents, Stripe-style event envelopes, and consistent error bodies.
Getting started begins with onboarding — the Maple team creates your developer app and issues your test credentials. Contact us to begin, then follow the Quickstart.