I am trying to register a webhook using oauth 2.0 . I could see that in the doc it is mentioned that we can use /rest/api/3/webhook but while using jira Server i could register using the old
webhook/1.0/webhook endpoints.
Now since the response type of the new /rest/api/3/webhook is very different from the older endpoint of webhook/1.0/webhook i need to do i lot of refactoring. So i want to know is there a way where i could use the older webhook/1.0/webhook with oauth 2.0 for jira Cloud .
thanks
@DependraKafley no, I’m afraid not.
If you are developing a custom integration, you would be able to use Basic authentication with API tokens as described in Registering a webhook using the Jira REST API (other integrations). We do not intend to enable the use of that API with OAuth 2.0.
With OAuth 2.0, you need to use the Dynamic Webhooks API as described in Registering a webhook using the REST API (for Connect and OAuth 2.0 apps).
Thank you for your response…
I still have a question though.
I am using ouath2.0 in my jira server there i am able to use /webhook/1.0/webhook endpoint and it works perfectly fine
And the other doubt i have is related to admin webhook… So if i go by the documentation for oauth2.0 even for admin webhook i have to use
/rest/3 version api ?
@dependrakafley1 Jira Server and Jira Cloud have evolved independently for a number of years. I believe OAuth 2.0 for Jira Cloud was introduced back in 2019, and a rather different variant for Server in 2022.
Webhooks registered by OAuth 2.0 apps (clients) are registered for the app itself. They are not admin webhooks, and they are not displayed in the UI for admin webhooks.
Okay I guess now i am convinced though I still have one more doubt
So even if I have to make admin webhooks through Oauth2.0 I would continue to use the same endpoints ?
Also I dont see any api where I could get the entire webhook details by passing the id of the webhook. So should i assume that there is no such api ?