Call Summary Webhook (Legacy / Raw Format)
Legacy call summary payload used by select partners (e.g., LeanTaas / Pinnacle Orthopedics). Hippocratic AI POSTs this JSON after each completed call.
Unlike the standard call-summary webhook (which delivers a flat, versioned {version, call_summary} envelope), this payload is split across a top-level call object (call metadata, dispositions) and json_summary object (clinical summary). Three rendered representations of the summary — pdf_summary (base64 PDF), html_summary, txt_summary — are also included.
Retry Policy: If the webhook delivery fails (non-2xx response or network error), Hippocratic AI will automatically retry the delivery 3-5 times with 30-minute intervals between attempts.
Compatibility
- New optional fields and enum values may appear without notice. Partners MUST ignore unknown fields and unknown enum values.
- Field removals, type changes, and enum-value removals are breaking and will be coordinated in advance.
- Optional fields are typically sent as "" / [] rather than omitted. Treat both as "no value".
- A partner receives exactly one of the two contracts (call-summary or call-summary-legacy). Confirm with your DA. Payloads are not interchangeable.
- Deliveries may be retried after non-2xx responses. call.call_id is stable across retries — deduplicate on it.
Payload
Response
Webhook received and processed successfully
Changes
Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.