# WebHook calls back - authorization header - HTTP reserved name issue

**URL:** <https://devforum.zoom.us/t/webhook-calls-back-authorization-header-http-reserved-name-issue/58929>\
**Category:** Feature Requests\
**Created:** [October 15, 2021, 11:32am UTC](https://devforum.zoom.us/t/webhook-calls-back-authorization-header-http-reserved-name-issue/58929 "2021-10-15T11:32:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ajay.prabhakaran](https://avatars.discourse-cdn.com/v4/letter/a/d07c76/32.png) [@ajay.prabhakaran](https://devforum.zoom.us/u/ajay.prabhakaran)\
**Post date:** [October 15, 2021, 11:32am UTC](https://devforum.zoom.us/t/webhook-calls-back-authorization-header-http-reserved-name-issue/58929/1 "2021-10-15T11:32:28Z")

</div>

We have implemented a Service endpoint (Java jersey JAX RS based) for the callbacks based on webhook APIs. The calls from Zoom include authorization header variable which includes the verification token from the app. The issue is, this is a name reserved for sending AuthN tokens and hence we are facing issues getting this through.

Why isnt zoom using a non-reserved HTTP header variable (e.g: verification\_token or so) so

**Which App Type (OAuth / Chatbot / JWT / Webhook)?**  
OAuth

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [November 14, 2021, 9:33pm UTC](https://devforum.zoom.us/t/webhook-calls-back-authorization-header-http-reserved-name-issue/58929/2 "2021-11-14T21:33:18Z")

</div>

Closed on November 14, 2021, 9:33pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.