Current public baseline
The current public developer baseline includes scoped API keys, menu item reads, order reads, signed webhooks and MCP list tools.
Developer Changelog.
Public policy for API, webhook and MCP release communication.
Changelog policy
Changelog entries must be factual, customer-impact oriented and aligned with implemented public surfaces.
No invented version history
Developer changelog entries are not invented. Public entries should be created from real releases and customer-impacting API changes.
Breaking changes
Breaking changes to endpoints, scopes, webhook payloads, rate limits, pagination or MCP tools require explicit migration guidance.
Deprecation policy
Deprecated public API behavior should keep a removal date, replacement path, customer impact and support contact.
Security changes
Security-relevant changes must say whether keys, webhook secrets, IP allowlists or consumer validation need customer action.
Provider-specific changes
Provider connector changes are published only after the provider integration is contracted, implemented and available for the customer scope.
Until public version history is published, developers should treat the API Reference and Webhooks pages as the current baseline.
Plan a clean restaurant rollout.
Talk through locations, POS devices, kitchen workflow, menu migration, API needs and security review before launch.