You can now add your own headers to the webhooks your campaigns send. This makes it easier to connect VoiceAIWrapper to systems that require authentication on incoming requests.

What's new

• Add custom headers to your webhooks. In a campaign's Settings → Webhooks section, each webhook now has a "Custom headers" area where you can add header name/value pairs and remove them as needed.

• Set them per webhook. Configure headers independently for your post-call webhook and your pre-call webhooks.

• Common use. The most common case is adding an authorisation or API-key header (for example, Authorization: Bearer your-token) so your endpoint can confirm the request really came from your campaign before accepting it.

A few headers are managed automatically and can't be overridden (such as Content-Type and the tenant identifier), and empty header names are ignored.