Server URL secret token does not work for Azure
# support
d
I have an Azure function set up with an endpoint I need to access with my Vapi bot. Currently it is calling my serverUrl, but the function is returning a 401 unathourized. My assumption is that the Server URL secret token does not have the correct header key, as this should be 'x-functions-key'. But I do not know how to set this manually
v
@DaVenthus To ensure that your VAPI bot can successfully access your Azure function, you'll need to set the correct header for the secret token. In VAPI, the header for the secret token is sent as
x-vapi-secret
. If your Azure function expects the secret token with a different header key, such as
x-functions-key
, you will need to configure your server to accept the
x-vapi-secret
header or modify the request within your VAPI bot to use the correct header key. If you have control over the Azure function, you could update its configuration to accept the
x-vapi-secret
header. If that's not possible and you need to set a custom header key, you might need to look into VAPI's documentation or settings to see if there's a way to customize the header key for the secret token. If you're unable to find the information you need or if you require further assistance with configuring your VAPI bot to work with your Azure function, please ask support for more info on this. They will be able to provide you with specific guidance tailored to your setup.
You can continue this conversation by mentioning me in the message.
d
I've found a solution within Azure, but it would be nice if the header key was modifiable on Vapi's end
7 Views