Refresh expired bearer token automatically

Not at this time, Daniel. If I see any news in this area, I'll come back here and drop an update.

Hi 1263082154109, any updates on this? This is such an important feature as you can see as stated by the other developers here. I need this as well to make my webhook work with obtaining a refresh token. Please provide an update or a workaround. Thank you.

Hi Madhanprabhu! That is correct, we still do not have this functionality available. The only available auth methods currently are Basic, Bearer token, and API tokens.

Hello Zendesk Community,

Is it still the same case now as 1900280398944 and 5742331406874 mentioned ? We have a listening endpoint for Zendesk webhook events and at this moment we recommended to use only OAuth2.0. Are we still not allowed to get the refresh tokens as part of webhooks ?

I have the same problem as @Aravindaraj J where NetSuite only issues OAuth 2.0 tokens with a refresh token, but Zendesk is only letting me enter a bearer token and has nothing that facilitates the refreshing part for webhooks

Hello Sue,
 
For Webhook authentication, you need to use the Basic authentication method for API token in the following format:
 
You can also visit this article for more information on how API token is used for authentication.

Hi 1263082320149

Wondering if you can help.

I want to create a webhook using the API Key for authentication.

However, the Webhook then asks for a Header name and Value

This is where I'm getting confused. I have tried using:

Header name: Authorization
Value: Bearer <my_api_key>

But I receive an "invalid token" error. I have verified that my API token is active and current. See below error and screengrab.

Do you know what needs to be entered into these fields to make the Webhook work?

Many thanks

Error:

{
    "error": "invalid_token",
    "error_description": "The access token provided is expired, revoked, malformed or invalid for other reasons."
}

Screengrab (Not sure what to enter into these fields)

Hey 1263758749190! Based on the token example you provided, it appears that you are using an API token, not a bearer token. Bearer tokens are opaque strings, and they're the predominant type of access token used with OAuth 2.0. You can find more information in our Developer Docs for the available Webhook Authentication methods.

Hi All,

I am trying to create a webhook with bearertoken, but it is not working, The same wehbook with basic authentication is working properly, but if i switch to bearer token, then it gives 401 error

{
    "error": "invalid_token",
    "error_description": "The access token provided is expired, revoked, malformed or invalid for other reasons."
}

I tried adding the token in all the possible format:

• aygaoWwEs4qTpNRkn71WacsxgHSzP1zpxogEEZ8g007
• abc@mymailbox.com/token:aygaoWwEs4qTpNRkn71WacsxgHSzP1zpxogEEZ8g007
• abc@mymailbox.com/aygaoWwEs4qTpNRkn71WacsxgHSzP1zpxogEEZ8g007
•  

what am i doing wrong

Hi 1900280398944,

Authentication seems to be a hassle to work with across various systems and platforms.

Allow me to suggest a solution that not only resolves the authentication issues, but also provides a host of additional features to make integrating ZenDesk and ServiceNow much easier and feature rich.

Exalate is a fully decentralised integration solution that will allow you to integrate ZenDesk with ServiceNow without the need for direct authentication as Exalate on ZenDesk will communicate to Exalate on ServiceNow it allows you to have full control on the info/data send and how this info/data is received and displayed. Plus allowing for data manipulation and setting up control flow.

Have a look and let me know if it fits you needs.

Kind regards,