mxAURA Developer Center

mxAURA is a composition and orchestration layer on top of HubSpot. HubSpot owns sending, CRM, timing and compliance; mxAURA owns composition (components → messages → pools → campaigns → flows, with cascade logic per contact), content hubs (embeddable article libraries), and multi-tenant distribution (agency → client).

There are two programmatic surfaces, and they share one authorization model:

Both are graded by the same scope families, rate limits and tenant boundary. Everything an API key can do, an MCP token can do — if it holds the scope.

Documents

1. Quickstart — a key, a first call, a first campaign simulation, in five minutes
2. Authentication — API keys, OAuth 2.1 tokens, scopes, the support profile
3. Conventions — envelope, pagination, errors, rate limits, idempotency, IP allowlists, headers
4. Resource reference — every family: components, brandings, pools, campaigns, flows, enrollments, dispatch, hubs, articles, publishing, subscribers, identity, folders, media, webhooks, ai
5. Webhooks — outbound events, signing, retries, a verified receiver in three languages
6. MCP guide — connect from Claude.ai, Claude Desktop, Cursor and others; the 21 tools; what the model can and cannot see
7. Examples — end-to-end recipes in curl, Node and Python
8. Security — what mxAURA enforces, what you should
9. Troubleshooting — every error code, what it means, what to do
10. Changelog

The machine-readable contract is at https://api.mxaura.ai/v1/openapi.json (OpenAPI 3.1, unauthenticated). Import it into Postman, Insomnia, or a code generator.

The model in one paragraph

A component (header, summary, signature, sender, template) is a reusable piece. A message composes components. A pool holds ordered messages. A campaign assigns pools and decides, per contact, which message comes next (the cascade). A flow governs the per-contact journey through campaigns. When a HubSpot workflow reaches the mxAURA action, dispatch selects the message, writes the resolved content to contact properties, and HubSpot sends the email. A hub is an embeddable library of articles that publishes to client sites through an embed key. An agency account composes once and distributes to its client accounts.

Every object belongs to exactly one account. The API only ever shows you yours — that boundary is enforced at the database layer, not by convention.