I am currently facing an issue with the Message Settings webhook logs returning a 403 Forbidden error. I have configured the X-VAPI-SECRET header in my server settings assistant; however, it appears that the header and its corresponding value are not being transmitted to the connected webhook endpoint, which is likely the cause of the error. To verify the webhook, I tested it using a cURL request, and it functioned as expected—confirming that the endpoint is operational and properly configured. This is an urgent matter as it is impacting a deployment scheduled to go live. I would greatly appreciate your prompt assistance in resolving this issue.

Vapi doesn’t send the X-VAPI-SECRET header by default instead, it uses X-Vapi-Signature when a secret is set.

I had left the server secret empty and defined on the server headers request. But after filling in the secret value the error has disappeared.

Glad it fixed

I noticed the VAPI server UI isn't saving my url or secret correctly. It seems like it cuts off the last character I type in. if I do "123" it saves it as "12". If I try to add "123" again it does the same. The url also reverts back to the old one I had set.

Can you send me your account email address as well a loom video? Will get this fixed.