Everything the Interface Does, Your Systems Can Do Too

How it works

The API exposes conversations, contacts, tickets, and leads over authenticated REST endpoints. Anything you can see in the interface, you can read or create programmatically, using your own field names where mapping is needed.

Webhooks fire on the events worth reacting to: a conversation started, a ticket created or closed, a lead qualified, a handover requested. Payloads are signed so your endpoint can verify they came from us.

• Authenticated REST endpoints for conversations, tickets, and leads
• Signed webhooks on the events that matter
• Retries with backoff when your endpoint is unavailable
• Field mapping so payloads match your own schema

Why an API beats waiting for a connector

Every business has one system nobody else has heard of: a bespoke ERP, an old stock database, a spreadsheet that runs the whole warehouse. Waiting for a native integration to that is not a plan.

With webhooks and a REST API, a developer can wire the important path, usually a lead into your CRM or a ticket into your operations system, in an afternoon.

Operational detail

Failed webhook deliveries are retried with exponential backoff and are visible in a delivery log, so a brief outage at your end does not silently lose events.

Rate limits are documented and generous, and test credentials are available so you can build against a sandbox before touching live conversations.