CallsAround API

REST API for lines, escalation chains, calls (with media), usage, SMS/voice notifications, and webhook subscriptions. Auth: Authorization: Bearer ca_(test|live)_…. Outbound webhooks: X-CallsAround-Signature: t=,v1=<hex hmac-sha256(${t}.${raw body})> — verify with the reference client (5-min tolerance); retries: 5 attempts with 1/5/25/120-minute backoff, then dead-letter; events: call.completed, emergency.dispatched, line.health_changed, call.uncovered, call.failed, usage.threshold, usage.exceeded, message.taken.

Every response is a JSON envelope: { ok: true, data, request_id } on success, { ok: false, error: { code, message, request_id } } on failure. Rate limit: 120 requests/minute per key. Agency keys act on their own org and all descendant client orgs.

Connecting a CRM or job platform (Zapier)

No native connector is required for most tools: point a webhook subscription at a Zapier Catch Hook (Webhooks by Zapier) and map the fields into any app with Zapier write actions — e.g. Albi (Create Contact / Create Project / Create Project Note), or thousands of others.

Recipe:

1. In Zapier, create a Zap with trigger Webhooks by Zapier → Catch Hook; copy the hook URL.
2. In the CallsAround dashboard (Developers → Add webhook subscription) or via POST /webhooks, subscribe that URL to message.taken (leads with content) and/or call.completed (every call; a taken message rides along in data.message).
3. Map data.contact_name, data.callback_e164, data.address, data.problem, and data.urgency into your app's action fields.

Zapier's Catch Hook does not verify signatures; if you need verification, use Zapier's Catch Raw Hook with a Code step, or any endpoint of your own (see the signature scheme under Webhook events below).