Developers

Everything you can build against QuantCX: the chat widget's JavaScript API, signed identity, custom apps, the REST API, webhooks, AI Actions and the MCP server.

QuantCX talks to your systems in both directions. Your site and servers can call QuantCX, and QuantCX can call endpoints you host. Every outbound call is signed or authenticated, goes only to public https:// addresses on port 443, and never follows redirects.

Your website and app

  • Embed and JavaScript API: the one-line snippet that adds the chat widget, and the QuantCX() commands to identify a visitor, open or close the chat, and log out.
  • Signed identity: your server signs a short-lived token for the signed-in user, and QuantCX shows them as Verified. The AI then treats them as a client and can use AI Actions marked verified-only.

Calling QuantCX

  • REST API: read contacts, conversations and tickets with incremental sync, and push contacts in bulk, with a workspace API key.
  • MCP server: connect Claude, ChatGPT, Cursor and other MCP clients to your workspace with OAuth or an API key.

QuantCX calling you

  • Webhooks: signed ticket.created and ticket.updated events, retried until your endpoint accepts them.
  • Custom apps: your endpoint returns a card that your team sees in the Desk side panel next to every conversation and ticket.
  • AI Actions: HTTP requests the AI can make to your systems during a chat, with input validation, optional approval and a full audit log.

Signatures at a glance

Webhooks and custom apps use the same signature scheme: the header X-QuantCX-Signature: t=<unix seconds>,v1=<hex>, where v1 is the HMAC-SHA256 of <t>.<raw body> under the signing secret. One verification function covers both; it is on the Webhooks and Custom apps pages.

Plan requirements

The REST API and the MCP server need API access, which comes with an active Premium plan or above. API keys are created by owners and admins under Settings > Channels & API > API Keys.