Webhooks
Truedy can send HTTP callbacks to your server when certain events occur (e.g. call completed, batch call status).Overview
- You provide a webhook URL in the dashboard or via API.
- Truedy sends POST requests to that URL with a JSON body and signature headers.
- You should respond with 2xx quickly; process asynchronously if needed.
Payload format
Each request includes:- Body: JSON with
event,timestamp, and event-specificdata. - Headers: e.g.
X-Truedy-Signature(or similar) for verification.
Event types
Truedy can send these event types to your webhook URL (depending on how your endpoint is configured):| Event | Description |
|---|---|
call.started | Call has started |
call.joined | Participant joined the call |
call.ended | Call ended (also sent as call.completed and normalized to call.ended) |
call.billed | Call billing event |
call.failed | Call failed |
batch.status.changed | Batch call status changed |
batch.completed | Batch completed |
voice.training.completed | Voice training finished successfully |
voice.training.failed | Voice training failed |
Security
- Verify the signature using the shared secret.
- Use HTTPS only for webhook endpoints.
- Idempotency: The same event may be retried; use
event_idor similar to deduplicate.
Retries
If your endpoint returns a non-2xx status or times out, Truedy may retry with exponential backoff. Implement idempotent handling so duplicate deliveries are safe.Public API and callbacks
Truedy’s backend receives callbacks from the voice provider (e.g.call.ended, call status) and can forward events to your webhook URL. The webhook URL and secret used for these outbound callbacks are configured in the Dashboard (e.g. Settings or Integrations) or via environment/config for your Truedy instance. Use the same signature verification and retry handling described above.
Need help?
- Configure webhook URL and secret in the dashboard or via the API.
- Check Error Handling for how to log and report issues using
request_id.

