Integration Overview
The real ways to integrate with Mozo today, and what isn't available yet.
This page sets accurate expectations before you dive into the reference pages. Mozo does not currently expose a public, API-key-authenticated REST API for third-party developers. If you're looking for "the API", what you actually want is one of the four integration surfaces below.
What exists today
| Surface | What it's for | Auth |
|---|---|---|
| Embed widget | Floating chat on your website | Signed session + origin allowlist |
| Hosted page | Shareable full-page chat link | Same as widget |
| Custom actions | Your agent calls out to your API or notifies Slack/email | Server-side env var, configured per agent |
| Lead webhooks | Your server gets notified when a lead is captured | Optional HMAC signature |
What doesn't exist today
- No tenant-issued API keys. There's no
Authorization: BearerAPI for calling Mozo programmatically from your own backend. - No public agent CRUD API. Creating, editing, and deleting agents is done through the dashboard (session-authenticated), not a documented external API.
- No native third-party connectors. There are no built-in Zendesk, HubSpot, Salesforce, Shopify, Slack app, Microsoft Teams, WhatsApp Business, Notion, or Zapier/Make integrations. If your marketing materials or older docs mention these, they describe a roadmap direction, not shipped functionality — the real extension points are custom actions (generic HTTP + Slack/email webhook) and lead webhooks.
If you want Mozo to talk to a specific tool that isn't listed above, the most reliable path today is pointing a Custom Action or a lead webhook at that tool's own API, or at an automation platform like Zapier or Make that then fans out to it.
Internal APIs
Routes under /api/agents/*, /api/documents/*, /api/website-sources/*, and similar are
used by the dashboard itself and require a logged-in session. They aren't a supported public
API surface and may change without notice — don't build external integrations against them.