Documentation Index
Fetch the complete documentation index at: https://developer.kallglot.com/llms.txt
Use this file to discover all available pages before exploring further.
Webhooks
Use webhooks when your backend should react to call lifecycle, recordings, delivery failures, etc. You register an HTTPS URL, subscribe to events, verify eachPOST, and acknowledge with 2xx quickly so Kallglot stops retrying.
How Webhooks Work
Setting Up Webhooks
1. Create a Webhook Endpoint
Create your developer account at kallglot.com, then create a webhook endpoint in the Developer Portal:- Go to Webhooks > Add Endpoint
- Enter your endpoint URL (must be HTTPS)
- Select which events to receive
- Save and copy the signing secret
2. Configure Your Server
Set up an endpoint to receive webhook events:3. Test Your Endpoint
Use the Developer Portal to send test events to your endpoint before going live.Event Structure
All webhook events follow this structure:| Field | Description |
|---|---|
id | Unique event identifier |
type | Event type (e.g., session.ended) |
api_version | API version that generated the event |
created_at | When the event was created |
data | Event-specific payload |
Event Categories
Session Events
| Event | Description |
|---|---|
session.created | A new session was created |
session.started | Session became active |
session.ended | Session ended |
Transcript Events
| Event | Description |
|---|---|
transcript.ready | Full transcript is available |
transcript.segment | New transcript segment (real-time) |
Recording Events
| Event | Description |
|---|---|
recording.ready | Recording is available for download |
recording.failed | Recording generation failed |
Analysis Events
| Event | Description |
|---|---|
analysis.complete | Analysis results are ready |
analysis.failed | Analysis failed |
Provider Events
| Event | Description |
|---|---|
session.provider.connected | Provider call connected |
session.provider.disconnected | Provider call disconnected |
Endpoint Requirements
Your webhook endpoint must:- Accept HTTPS POST requests
- Respond within 30 seconds
- Return a 2xx status code on success
- Be publicly accessible (no localhost)
Best Practices
Respond quickly
Respond quickly
Process webhooks asynchronously. Return a 200 response immediately, then process the event in a background job.
Handle duplicate events
Handle duplicate events
The same event may be delivered multiple times. Use the
id field to deduplicate:Verify signatures
Verify signatures
Always verify webhook signatures to ensure events are from Kallglot. See Signatures.
Log all events
Log all events
Log incoming webhooks for debugging and audit purposes:
Monitor delivery
Monitor delivery
Check the Developer Portal for webhook delivery status and failures. Set up alerts for repeated failures.
Testing Webhooks
Using the Developer Portal
- Go to Webhooks > select your endpoint
- Click Send Test Event
- Choose an event type
- View the delivery log