Jira: not receiving webhook events?
Apideck receives Jira changes through native Jira webhooks: when a consumer connects Jira, Apideck registers a webhook in their Jira site and keeps it up to date. If a connection looks healthy but no Jira events arrive, check the points below.
The most common cause: one Jira account used by several connections
Jira only lets an app register one webhook address per Jira user. Atlassian's own tracker documents this (JRACLOUD-78956).
So if several connections are authorized with the same Jira account, only one of them can own the webhook, and only that one receives events. The others look connected and healthy but get no events. This happens in two situations.
Several consumers in the same Apideck application, same Jira account
For example, two of your consumers both connect using the same Jira user (often a shared admin or integration account). Jira sends events only to whichever connection registered the webhook first.
Fix: connect each consumer with a different Jira user. This is a Jira limitation, so it can't be worked around on the Apideck side.
Several Apideck applications, same Jira account
For example, you have separate Apideck applications for production and staging, and both connect to the same Jira account. If both use the same Jira OAuth app, for example Apideck's default credentials, they compete for one webhook.
Fix: configure your own Jira OAuth app for each Apideck application (in the Jira connector's configuration), so each application registers its own webhook.
Other things to check
Your webhook subscription in Apideck is enabled and includes the issue-tracking events you need (for example
issue-tracking.ticket.created).The connection is healthy. If it needs re-authorization, events stop. See Why did my connection stop working?
Your endpoint responds with a 2xx within 60 seconds. See Are webhooks retried when they cannot be delivered?
Reconnecting re-registers the webhook. If a connection was set up before your webhook subscription existed, or something else changed in Jira, disconnecting and authorizing the connection again makes Apideck register its webhook again (unless another connection on the same Jira user already holds it, see above).
Still nothing?
Contact Apideck support through the Customer Portal (the Requests link at the top of this help center), your Slack channel with us, or support@apideck.com. Include the consumer ID and the Jira user each connection was authorized with.
