adding webhooks to different environments: dev, staging and production | ElevenLabs | Page 1

AI-generated Answer for ssaue_19420

Short answer: ElevenLabs doesn’t expose a first‑class “environment” concept for webhooks. To separate dev/staging/prod, create distinct webhooks (unique callback URL and secret) in the dashboard and attach/enable them per product/feature where you need them.

How to set it up

Create one webhook per environment in Settings → Webhooks. Each webhook has its own secret; verify requests using the ElevenLabs-Signature HMAC header. Webhooks can be disabled or auto‑disabled after repeated failures. (elevenlabs.io)
Agents Platform — Post‑call:
- Enable post‑call webhooks and point each agent/environment to the correct endpoint. ElevenLabs documents two post‑call types: post_call_transcription and post_call_audio. As of Mar 31, 2025 you can override post‑call webhook settings at the agent level. Note a format migration for transcription webhooks on August 15, 2025—test against this in non‑prod first. (elevenlabs.io)
Agents Platform — Twilio inbound personalization:
- Configure the “personalization” webhook endpoint used during call setup. You can set different endpoints per agent, so create dev/staging/prod agents that each reference the appropriate URL. (elevenlabs.io)
Speech‑to‑Text (asynchronous):
- Link your environment‑specific webhooks to Speech‑to‑Text events in the dashboard, and set webhook: true on conversion requests so completions are delivered to the linked endpoints. You can include webhook_metadata in requests (e.g., { env: "dev" }) and receive it back in the payload for routing/auditing. For local dev, use an HTTPS tunnel (e.g., ngrok). On STT webhooks, 5xx responses are retried; 2xx are treated as success. (elevenlabs.io)

Operational tips

Keep a separate secret per environment and validate ElevenLabs-Signature = "t=timestamp,v0=hex(hmac_sha256(timestamp + '.' + body))". Respond 200 quickly; manage processing async to avoid auto‑disable due to repeated failures. (elevenlabs.io)
Inventory/health‑check your configured webhooks programmatically with GET /v1/workspace/webhooks (name, URL, disabled/auto‑disabled flags, recent failure info). Creation/enable/disable is documented via the dashboard UI. (elevenlabs.io)

If you share more about which ElevenLabs features you’re using (Agents, STT, etc.), I can map exact screens/fields for your environment split. (elevenlabs.io)

#adding webhooks to different environments: dev, staging and production