Facing a new issue. We recently renamed and changed our organization settings. Since then, I realize the custom headers we had previously set are no longer sent to our webhook. And whenever I try to set them in the dashboard UI, I see a "You have unsaved changes" warning, and the headers are not set apparently. Any gotchas I need to pay attention to? Thx in advance for the quick help!

This is a known bug in the dashboard UI that prevents headers from being saved properly. As a workaround, use the API to add your webhook headers:

bash
curl -X PATCH 'https://api.vapi.ai/assistant/{assistant_id}' \
-H 'Authorization: Bearer YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
  "server": {
    "url": "https://your-server-url.com",
    "secret": "your-secret-key",
    "headers": {
      "custom-header": "header-value"
    }
  }
}'

The issue will be fixed in dashboard v2. Sources: - [Discord conversation about webhook headers issue](https://discord.com/channels/1211482211119796234/1334552736133546076) - [Discord conversation about API workaround](https://discord.com/channels/1211482211119796234/1341692740454584331) - [Discord conversation about known bug](https://discord.com/channels/1211482211119796234/1336715819333193740)

@jeromec8194 You can use postman for this if you wish - it is really easy to use the API through there and it's free.

Thx @SlaviSavanovic ! Using the api isn’t really an issue. I’m more annoyed by doing this at the agent level, as it means updating all our agents. I’ll check in the docs if there are organisations related endpoints

Try setting headers via API instead of the UI, and also clear your browser cache..

thx @Kings_big💫 - afaik there are no endpoints to set organisation settings. So that leaves me with doing it at the assistant level, which I'd rather avoid because it implies updating all assistants. If this is indeed a dashboard UI bug, it would be great if we could get an ETA on when this could be fixed

Hey, really sorry for your experience. If possible, could you record a loom video describing this error/behavior or inconsistency in the dashboard with the steps to reproduce it? That way, I can share this with my team, and we'll take a look. We'll even try to reproduce the same so we can fix it for you. Also, I'll request you to share your organization ID.