Call webhooks

A Studio receptionist can post each call to your own server as it happens — when it starts, when it ends, and when the post-call analysis is ready. Set it up in Settings → Webhooks.

Set it up

Add your endpoint

Enter a public https:// URL (port 443, IPv4), choose the events you want, and save. Each Studio agent has one endpoint, covering both the calls she answers and the calls she places.

Save the signing secret

A whsec_... secret is shown once. Saving the endpoint again makes a new one.

Send a test event

Send test event posts a webhook.test event, and the delivery history shows whether your server accepted it.

Events

Event	When
`call_started`	The call connected. A call that fails before connecting may have no start event.
`call_ended`	The call hung up. Usually includes the transcript.
`call_analyzed`	The summary and extracted details are ready. Can arrive after `call_ended`.

Payload

{
  "id": "4f1c2a9e-...",
  "event": "call_analyzed",
  "created_at": "2026-10-01T12:00:00.000Z",
  "call": {
    "call_id": "call_abc123",
    "direction": "inbound",
    "from_number": "+12125550100",
    "duration_ms": 184000,
    "transcript": "Agent: Thank you for calling…",
    "call_analysis": {
      "call_summary": "Caller was rear-ended on the 405 last Tuesday…"
    }
  }
}

call can also carry call_type, to_number, recording_url, start_timestamp, end_timestamp and disconnection_reason, depending on the event. Nothing else is sent — no provider credentials or internal metadata. Treat transcripts and recordings as confidential.

Respond fast, then verify

Return any 2xx within 10 seconds and do your work afterwards. Anything else — including a redirect — counts as a failure and is retried after 1, 5 and 30 minutes (four attempts in all). Events can arrive out of order or more than once: deduplicate by id. Every request is signed with X-Lawtte-Id, X-Lawtte-Timestamp and X-Lawtte-Signature (v1= plus an HMAC-SHA256 of id.timestamp.rawBody, keyed by your secret). The verification code is in connector keys and webhooks.

What Lawtte does on its side

You don’t need a webhook for the basics. Every call is already in Conversations in your dashboard, and after a call the receptionist emails your team the intake summary, and can email the caller a booking link when they ask for one. The webhook is for getting the same call into your own systems.

Practice-management and CRM sync (Clio, MyCase, Lawmatics and others) is set up per firm by the Lawtte team on managed plans. It isn’t something a webhook turns on. Book a call if you need it.

Get started

Guides

Set it up

Events

Payload

Respond fast, then verify

What Lawtte does on its side

​Set it up

​Events

​Payload

​Respond fast, then verify

​What Lawtte does on its side

Set it up

Events

Payload

Respond fast, then verify

What Lawtte does on its side