Maple developer resources

Connect restaurant software to Maple, or let an agent read Maple's public product resources. The partner Developer API and this website's public API are separate services with separate contracts.

Maple Developer API for POS and platform partners

The partner API lives at https://api.maple.inc/v1, with a separate sandbox at https://api.staging.maple.inc/v1. Start with the published guides and your approved integration scope.

• Maple Developer API — POS and platform partner API overview
• Maple Developer API OpenAPI — Partner API operations and schemas
• Maple API authentication — Bearer keys, scopes and onboarding
• Maple API environments — Sandbox and production hosts
• Maple API webhooks — Subscriptions, signatures and delivery handling
• Maple Developer API errors — Partner API error tags and recovery

Authentication and access

The partner API uses server-side Bearer API keys issued during Maple onboarding. Keys select an environment and scopes; location grants also limit access. Follow the Maple authentication guide. The three website operations below and the public MCP tools require no credentials. Do not send partner API keys to this website.

Maple website API and OpenAPI

The maple.inc marketing API is described at https://maple.inc/openapi.json (also listed as Maple API docs at /api-docs). The RFC 9727 catalog is https://maple.inc/.well-known/api-catalog. Current version is v1 in the URL path: GET /api/v1. Unversioned /api is an alias of /api/v1. Errors use RFC 9457 application/problem+json with a stable code, a human-readable message (same as detail), and a hint. Example: GET /api/v1/subscribe returns 405; an unknown /api/v1/… path returns 404.

Website API versioning and deprecation

Breaking changes ship as /api/v2. Additive fields on v1 are not breaking. When a version is retired, every response for that version will include the RFC 9745 Deprecation header (a Structured Field Date, such as @1798761600) and the RFC 8594 Sunset header, with at least 90 days between them. Sunset uses an HTTP-date, for example Thu, 01 Apr 2027 00:00:00 GMT. A Link with rel="deprecation" points to the policy and migration guide; rel="sunset" points to the retirement notice. v1 is current and does not send retirement dates. Responses include API-Version: 1 and a link to this policy. This 90-day policy covers maple.inc/api/v1; it does not declare a lifecycle policy for the separate partner API.

Website API errors

All documented 4xx and 5xx responses reference the OpenAPI Problem schema and use application/problem+json. Branch on code and HTTP status; message and detail explain the failure. Follow Retry-After when supplied. The partner API has its own typed error contract.

Maple MCP server

Agents can call Maple tools over Model Context Protocol Streamable HTTP at https://maple.inc/mcp. The server card is https://maple.inc/.well-known/mcp.json (also /.well-known/mcp/server-card.json). Tools are read-only: product, pricing, integrations, and these developer links. There is no merchant-data API on this host.

Product docs, webhooks, and help

• Maple Docs — POS setup, product guides, and the developer API. Machine index: docs.maple.inc/llms.txt
• Maple Help Center — getting started and troubleshooting
• Maple Developer API webhooks — subscriptions, signature checks and delivery handling. This website does not expose a public webhook-management API.

Maple CLI

Maple CLI setup and commands — download the read-only command-line client for public resources and scoped partner API reads.

For AI agents

• llms.txt — curated Maple site index
• llms-full.txt — full markdown dump
• /developers.md — this page in markdown
• sitemap.xml
• Page markdown: /index.md, /pricing.md, /product.md

Sales and support: contact Maple.