REST API
Use tenant-scoped endpoints for contacts, conversations, tickets, knowledge, automation, reporting, staff, billing, and integrations.
Connect customer operations without weakening the boundary.
Use authenticated APIs, scoped keys, signed webhooks, SDK foundations, a domain-validated widget, and encrypted channel configuration.
Scoped API keys
Create one-time visible secrets, assign scopes, set expiry, monitor use, and revoke access without sharing staff passwords.
Signed webhooks
Receive operational events with delivery logs, signatures, retry handling, and explicit endpoint controls.
Widget and SDKs
Install the browser widget with one domain-validated snippet. JavaScript, React, Flutter, Android, and iOS SDK foundations support deeper experiences.
Email through your SMTP server
Workspace administrators can open Channels → Email via SMTP after signing in. Configure host, port, encryption mode, username, password, From address, and a default subject. Credentials are encrypted at rest and the API never returns saved passwords.
SMTP host smtp.your-company.com
Port 587
Encryption STARTTLS
Username support@your-company.com
From address support@your-company.comUse a dedicated sending identity, a provider-specific application password where supported, SPF/DKIM/DMARC, and the built-in test action before production use. Never paste credentials into a support message.
Authentication model
Browser sessions use short-lived access tokens with refresh rotation. Server integrations should use a scoped API key or integration-specific OAuth flow. Do not expose server secrets in public widget code.
Need an integration review?
We can review channel, webhook, AI-provider, data, and authentication requirements before implementation.