You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
The webhook documentation and API documentation do not mention how to authenticate a webhook sent to the configured URL. Is there a supported way to do this?
Typically I'd expect a signature to verify or a header with an API key but I don't see either in the requests.
I could hard code an API key into a query param on the configured URL but that seems less than ideal.
Any help would be much appreciated.
Hi, @ben_walford! Welcome to the community!
If I understood your question correctly, you would like to authenticate the webhook destination servers, is that correct? If that’s the case, unfortunately, we currently don't have a way to do this as this feature is not available yet. We do have a feature request for this as you can see in the link below:
I've linked your question to this feature request. Please consider adding yourself as a watcher, so you get updated as we make progress with this. If you are not familiar with our Feature Request Policy, you can learn more about it here:
So, as a workaround, you can pass the credential using HTTPS by using:
https://<username>:<Password>@<URL>
Please, feel free to share any additional questions regarding this subject.
Kind regards,
Caroline
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.