I’m an engineer from a team working on Jira webhooks. I will try to answer your questions.
We have >100 webhooks actively syncing data from multiple projects. What happens to them?
Nothing will happen to your already registered webhooks. We are introducing a limit only for creating and enabling new ones. Everything else will be working as it is working now.
Will I be restricted to create new ones?
Yes, that’s the idea. If you need to have more than 100 webhooks active at the same time, please reach out to us, e.g. through customer support. We can work out some solution.
manual admin registered webhooks will get the limit imposed whereas REST API still works without any limits? Is that correct?
The thread you linked talks about the warning panel that appears when you reach 50+ active webhooks. The limit is a slightly different thing.
We are limiting the number of active Jira admin webhooks that you can create on a single Jira instance. This means that both the admin panel will limit this action and the REST API that is used for the creation of the same kind of webhooks.
This affects the following REST APIs:
That means, that these APIs will return an error if you try to create or enable a webhook that would breach the limit.
For example, you have 100 enabled webhooks and you’re using the
POST /rest/webhooks/1.0/webhook endpoint to create a new one. You will receive an error that it’s not possible due to the limit on the number of webhooks.
The same happens if you currently have, let’s say 256 webhooks. Then you want to create another webhook with API or UI and you will receive an error.
None of those 256 webhooks that you had before the limit was introduced are affected. So you can still use them but won’t be able to add new ones.
We use OAuth 1.0 which comes under other integrations of webhooks, does that change anything ?
The authentication method doesn’t matter when it comes to limits. If you’re using the REST APIs listed above, you will be affected. As I said, please reach out to us directly if it’s a breaking change for you, and we will try to work out a solution. Hopefully, one that won’t be disruptive for you in the following months.
I hope that made the webhook change a little more clear!