Announced on | Rollout starts |
March 30, 2023 | March 30, 2023 |
Zendesk is excited to announce that you can now use API key authentication and define additional headers when configuring webhooks.
What's changing?
There are two changes to the webhook configuration options: API key authentication and custom headers.
Authentication is required when your webhook is integrating with a secure endpoint. In addition to basic and bearer authentication, you now also have the option to use API key authentication. When you use API key authentication, you define a special custom header and value that is used to authenticate the webhook and the data it sends.
Additionally, admins can add up to five custom headers. You can use custom headers to integrate with endpoints that have unique header requirements, but we don't recommend that you use them to send sensitive information, such as authentication details.
Why is Zendesk making this change?
We heard from customers that they need more flexibility in how they connect Zendesk to other systems and services. With support for custom headers, customers are enabled to connect Zendesk to even more systems and support powerful cross-system workflows and data synchronization.
What do I need to do?
No action is required. This change is automatically being rolled out to all accounts. The next time you edit an existing webhook or create a new webhook, these options will be available to you. For more information, see Creating webhooks.
3 Comments
That's awesome!
You basically solved every issue I had while using Webhooks. Thanks!
https://internalnote.com/shortcomings-of-zendesk-webhooks/
🥳🥳🥳
Hey Zach Anthony,
FYI There's no mention of the new API Key authentication listed as an auth method in the Creating webhooks guide.
Might need to arrange for it to be updated. :)
Great call out Amie (successcx), I'll be sure to arrange to have that updated!
Please sign in to leave a comment.