The API, webhooks and Zapier

Client workspaces open up to the outside world under Settings.

API keys. A client can create scoped API keys, shown once at creation, prefixed so they are recognisable in code. The REST API covers the core objects of the workspace: contacts, products, orders and more, so custom scripts and integrations can read and write real data.

Webhooks. Outgoing webhooks fire on workspace events, eighteen of them, including new contacts, new orders and member signups. Each webhook gets a signed payload so receivers can verify authenticity. Delivery is queued and retried, and a delivery log shows what fired and what the receiver answered.

Zapier. The API and webhooks are what Zapier speaks to: trigger a Zap when a contact is created, or push a new row from a spreadsheet into contacts. If your client can describe the automation in one sentence, it can usually be built in a few minutes.

Claude and AI tools. The workspace also connects to Claude as a set of tools over the Model Context Protocol; see Connecting Claude.

A note on safety: API keys and webhooks are per client and scoped to their own workspace. No key can read another client's data.