Built to work with everything around it
Integrations use the REST API with scoped tokens, webhooks push events to your systems, and the desk is an MCP server, so AI assistants can work cases as the person who connected them.
How it works
The REST API lives under /api/v1 and is described as OpenAPI 3.1, with a reference on every desk. People create tokens with scopes, an optional unit limit and an expiry. A token is shown once and stored only as a hash, and it never sees more than the person who made it.
Webhooks post signed JSON to your systems after automations have run, signed with HMAC-SHA256, with retries and backoff, a delivery log, test events and redelivery. Plugins add their own events.
The MCP server is at /mcp on your desk. Claude, ChatGPT and other assistants connect through OAuth, or with a token for tools like Claude Code. Settings → AI assistants shows the address, ready-made commands, the tools you may use and your connections. Assistants draft replies first; an agent decides whether to send them.
Every write by a token and every tool an assistant uses is in the audit log, and timelines show which integration made a change.
What it includes
OpenAPI 3.1
A described REST API with a reference page on every desk.
Scoped tokens
Read, write and reply scopes, a unit limit, an expiry and a reminder before it ends.
What tokens can’t do
Never sign-in settings, users, teams, roles, the installation or tokens themselves.
Signed webhooks
Case and agreement events plus plugin events, with HMAC signatures, retries and a delivery log.
MCP server
Search, read, create and update cases, add notes, draft and send replies, find contacts and accounts, with plugin tools when they are on.
OAuth for assistants
Connect claude.ai, Claude Desktop or ChatGPT, and disconnect from your account.
Drafts first
An assistant’s draft waits on the case until someone uses it.
Form submission API
Post requests from a browser or from your server.