Passing API Header in HTTP Target

I too agree that this needs to be addressed. In order to bypass this limitation, I had to create a web function in Azure that receives the "Zendesk" limited feature way, and does it appropriately on the other side but now I have to introduce another system in the middle to do this, which introduces costs, potential issues etc. Can we please address the root cause of the issue by allowing a simple customization of the auth headers?

Has anyone found a solution to this? The webhook feature is useless without the ability to pass a token in the header.

Please, add ability to set custom auth headers for webhooks. Lack of that makes webhook feature useless.

Also wishing for something more modern than basic auth. Services today often require a bearer token or custom auth headers. Please allow us to set custom headers in outbound messages.

Another vote for this... basic auth really isn't very helpful any more. I need the ability to pass in a Bearer Token in the header.

Looking forward to an update on this from the zendesk team

AWS API Gateway doesn't support basic auth. Please add the ability to set headers to support API Keys.

Unfortunately basic auth is far less than standard now days and would mean creating another form of authentication for my APIs just to have Zendesk make a POST request.  The only reason we even need this is because the Zendesk API doesn't allow you to specify which custom field you are searching for when looking for a custom ticket field with a specific value.

+1

Hi,

Just bumping up this discussion since we would also appreciate this functionality in one of our use cases of passing info from Zendesk to a 3rd party application with customized authorization headers. 

HeyO Richard,

Apologies for the delay in replying to you! Our support team should be able to see whether authentication information is being passed successfully to Zendesk in your requests. 

Depending on the action being taken, I would either expect a 401 or 403 error in response to the request. Are those what you're seeing? If so, I recommend reaching out to support@zendesk.com with your subdomain and an example of the request you're making (without credentials for security's sake) so that folks can look through logs for those.