#Webhook can be set at level of workspace only for TTS API???
1 messages · Page 1 of 1 (latest)
Short answer: Yes—webhooks are configured at the workspace level (created/listed via /v1/workspace/webhooks) and are managed by workspace admins. They are not specific to the TTS API. (elevenlabs.io)
Details:
- Supported webhook events currently include items like post-call transcription and voice-removal notices; there is no documented TTS “synthesis complete” webhook event. (elevenlabs.io)
- For Agents, you can enable post-call webhooks at the workspace level and (since Mar 31, 2025) optionally override settings per agent. (elevenlabs.io)
- TTS is used via synchronous/streaming (HTTP/WebSocket) calls; webhooks are not part of TTS request flow. (elevenlabs.io)
If you need event-style handling around TTS, you’ll typically implement it in your own app logic (e.g., after the HTTP/streaming response completes). (elevenlabs.io)
Sources:
Create Workspace Webhook | ElevenLabs Documentation
Webhooks | ElevenLabs Documentation
Post-call webhooks | ElevenLabs Documentation
Text to Speech (TTS) API - ElevenLabs
Text to Speech (TTS) API - ElevenLabs
Ah.. ok when I start the call and when Initialization data with variables is takes, I can simply override the webhook URL?