unable to create webhook related to work log, showing error Invalid event ids

[Ralvie]

Hi everyone,

I’m trying to create a webhook for work log create, update, and delete events in Jira. However, I’m running into an issue where the response is not as expected.
Could someone guide me on how to properly create and configure a webhook for these operations? I’m currently using this API and payload:
POST: https://api.atlassian.com/ex/jira/4391e754-b51e-468f-b211-df307b329a0e/rest/api/3/webhook

NOTE: I am not integrated TEMPO App and using native.

Any help or suggestions would be greatly appreciated.
Thank you!

[Arkadiusz Wroblewski]

Hello and welcome @Ralvie 

@Himanshu Tiwary is only partly right here

The event names themselves look fine. worklog_created, worklog_updated, and worklog_deleted are valid Jira webhook events in general.

But the part that does not fit is the way you are registering the webhook.

Your example is using the dynamic webhook endpoint POST /rest/api/3/webhook with the url + webhooks array format. For that registration method, Atlassian only supports a limited set of events, and worklog events are not part of that list. That is why Jira returns Invalid event ids specified: [worklog_created].

In other words:

- the event name is not the real problem

- the endpoint / registration model is.

[Himanshu Tiwary]

Hi @Ralvie 

This normally occurs because the event IDs that you are sending in your payload do not match what Jira is expecting.

Here are the accepted IDs for worklogs in Jira:

worklog_created , worklog_updated , worklog_deleted

Sending anything other than the above will result in an “Invalid event ids” error in Jira.

Example of a valid payload would be:

JSON

{

    "name": "Worklog Webhook",

    "url": "https://your-endpoint.com/webhook",

    "events": [

        "worklog_created",

        "worklog_updated",

        "worklog_deleted"

    ]

}

Additionally, make sure that:

You use OAuth 2.0 / API token with proper scopes

cloudId parameter is correctly defined in your URL

There are no extraneous spaces in your event ID