Help centre · Step-by-step manual
Public API and customer MCP
Choose the appropriate workspace and branch. Your plan, enabled modules and team permissions determine which actions are available.
Public API and customer MCP
- Open Developer as the owner and consult the live API reference for the supported operations. Create a key with only the required scopes, branch and expiry.
- Keep the key on a trusted server. For supported writes, send an
idempotency keyand the current record version when required. - Revoke unused keys.
Customer MCPuses its own credentials through Connect your AI; its read-only tools still enforce module access and permissions.
On this screen
Online · Developer guide
Connect your own software with keys you control. Choose scopes, expiry and an optional branch. Keys never grant a module your account does not have.
Branch keys can read branch records and use branch modules. Catalogue, customer, CRM, HR and subscription endpoints require an account-wide key.
Developer access · AI access · Can see
Online · Developer access
Connect your own software with keys you control. Choose scopes, expiry and an optional branch. Keys never grant a module your account does not have.
Keep it like a password: anyone with this key reads what its scopes allow until you revoke it. We keep only a hash.
Branch keys can read branch records and use branch modules. Catalogue, customer, CRM, HR and subscription endpoints require an account-wide key.
Developer guide · All products · Your new key — copy it now. It is shown only this once. · New key · Name · Valid for days (1–365) · Branch · All branches · Can see · Make the key · Expires · Revoke · Revoked · API activity
