Integration patterns
Three ways to wire adaptlive into the rest of your stack — direct REST API, outbound webhooks, and the Zapier app. They aren't mutually exclusive; most production integrations combine at least two.
Pick a starting point
| Use case | Go to |
|---|---|
| Pull or mutate adaptlive data from your backend, on demand. | REST API |
| React to events as they happen — call ended, SMS received, draft approved. | Outbound webhooks |
| Wire adaptlive into other SaaS tools without writing code. | Zapier app |
| Backfill a fresh adaptlive workspace with historical records. | REST API + chat to us |
REST API
JSON over HTTPS. Bearer-token auth with READ / WRITE / ADMIN scopes. OpenAPI 3.1 spec at /openapi.json.
Outbound webhooks
HMAC-SHA256 signed event POSTs to your endpoint. Replay-protected. Sixteen event types across calls, SMS, voicemails, drafts, facts, and work records.
Set up webhooksZapier
14 triggers and 7 creates / searches against the REST API. No code, no servers — paste your API key and pick the trigger.
Explore ZapierCommon combinations
Event-driven CRM sync
Subscribe to work_record.created + draft.approved. On each event, your handler reads the full record via GET /v1/work-records/{id} and upserts it into your CRM.
Backfill + ongoing sync
Paginate the REST API once to seed historical state, then keep up with new activity via webhooks. (Same pattern Stripe recommends for their API.)
Notifications via Zapier, data via API
Use the Zapier signal_fired trigger for a Slack ping, but keep the canonical record writes in your own backend via the REST API.
Getting started
Most integrations start with a webhook subscription pointed at your endpoint, then add direct REST calls for backfill and on-demand reads.