Short answer: In the native Twilio integration, ElevenLabs sets and manages Twilio webhooks (including StatusCallback) automatically. There is no documented option to override the StatusCallback URL or change what that ElevenLabs endpoint does.
What’s documented
“Automatic Configuration: ElevenLabs automatically configures voice webhooks for your Twilio number” in the native integration. (elevenlabs.io)
The Twilio number is “automatically configured with the correct settings” when you import it; no user-configurable field for custom callbacks is shown. (elevenlabs.io)
The outbound-calling API exposes agent_id, agent_phone_number_id, to_number, and optional conversation_initiation_client_data—there’s no parameter to supply a StatusCallback URL. (elevenlabs.io)
Post-call webhooks are the supported way to receive outcomes. For Twilio calls, the metadata ElevenLabs sends to your webhook includes the Twilio StatusCallback body for call-initiation failures. (elevenlabs.io)
Your options
If you only need results/events, enable Post-call webhooks and consume the Twilio metadata ElevenLabs forwards. (elevenlabs.io)
If you must control Twilio StatusCallback yourself, don’t use the native integration. Instead:
Build your own Twilio application that streams audio to the ElevenLabs Agents WebSocket and set your own StatusCallback in Twilio. ElevenLabs provides a custom Twilio outbound guide for this approach. (elevenlabs.io)
Or use SIP trunking with ElevenLabs, where you control your carrier-side signaling and any provider callbacks. (elevenlabs.io)
If you’d like, I can point you to the exact sections to turn on Post‑call webhooks or outline the minimal custom Twilio app to keep full control over StatusCallback. (elevenlabs.io)
Here’s how to enable post‑call webhooks for Agents:
Create a webhook in your ElevenLabs dashboard settings (General settings → Webhooks). Add your HTTPS callback URL and set up HMAC verification; you’ll validate the ElevenLabs‑Signature header on receipt. (elevenlabs.io)
In Agents Platform → Settings, enable Post‑call webhooks for the workspace and select which events to send:
post_call_audio (base64 MP3 of the whole call; toggle “Send audio data” on)
call_initiation_failure (metadata about failed outbound call attempts) (elevenlabs.io)
If needed, override at the individual agent level (agent webhook overrides) for the audio webhook toggle. (elevenlabs.io)
Operational notes:
Your endpoint must return HTTP 200; after ≥10 consecutive failures with no success in the last 7 days, webhooks auto‑disable. For HIPAA mode, failed webhooks are not retried. (elevenlabs.io)
You can allowlist ElevenLabs’ static egress IPs for webhook delivery if your firewall requires it. (elevenlabs.io)
tough mulch
magic quail