Webhooks created through REST API not visible in Jira admin panel [PHP]

Other Questions Jira
1

I managed to create webhooks using the REST API successfully and can retrieve them through API calls. However, these webhooks don’t show up in the Jira administration dashboard. Here’s my implementation:

<?php
$webhook_endpoint = 'https://api.atlassian.com/ex/jira/'.$instance_id.'/rest/api/3/webhook';
$payload = <<<JSONDATA
    {
      "url": "https://webhook.site/f4a8b2c1-9e6f-4b2a-8c75-3d4e5f6a7b8c",
      "webhooks": [
        {
          "events": [
            "jira:issue_updated"
          ],
          "fieldIdsFilter": [
            "summary"
          ],
          "jqlFilter": "project = MYPROJECT"
        }
      ]
    }
JSONDATA;

$curl = curl_init();
curl_setopt($curl, CURLOPT_URL, $webhook_endpoint);
curl_setopt($curl, CURLOPT_POSTFIELDS, $payload);
curl_setopt($curl, CURLOPT_RETURNTRANSFER, true);
curl_setopt($curl, CURLOPT_CUSTOMREQUEST, 'POST');
curl_setopt($curl, CURLOPT_HTTPHEADER, [
    'Accept: application/json',
    'Content-Type: application/json',
    'Authorization: Bearer ' . $token_data['access_token']
]);

$response = curl_exec($curl);
$status_code = curl_getinfo($curl, CURLINFO_HTTP_CODE);

if (curl_errno($curl)) {
    echo 'cURL Error: ' . curl_error($curl);
}
curl_close($curl);

echo 'Status: ' . $status_code . '<br>Result: ' . $response;
?>

The API returns success responses but I cannot locate these webhooks in the Jira admin section. Also, when I modify issues that should trigger the webhook, no payload gets sent to my endpoint. What could be causing this issue?

2

I had the same problem with our ticketing system webhooks. You’re creating application webhooks when you need project-specific ones. Switch to /rest/api/3/project/{projectIdOrKey}/webhook instead of the global endpoint. Your fieldIdsFilter is wrong too - use the actual field ID for “summary”, not the display name. Check your field mappings. That JQL filter needs proper escaping. Spaces in project names will break things silently. For the delivery issues: make sure your endpoint accepts POST requests and responds within 10 seconds. Jira gives up if you keep timing out or throwing errors.

3

check your atlassian api token permissions - you’ll need both webhook:write and webhook:read scopes. that endpoint creates app-level webhooks, not project ones. try /rest/webhooks/1.0/webhook instead - works way better for project-specific stuff. your payload structure’s off too.

4

Been wrestling with Jira webhooks for years - the API complexity is exactly why I ditched direct integrations.

Your code’s fine, but you’re fighting Atlassian’s messy webhook setup. REST API webhooks work differently than admin panel ones. They function but debugging is hell.

I switched to Latenode for our Jira stuff last year. Instead of battling webhook endpoints and token headaches, I built a simple scenario that polls Jira for changes and triggers actions when fields update.

You get a visual workflow editor, built-in error handling, and way better logging than Jira’s delivery system. Easy to add filters, transformations, or route to multiple places without code.

Saved me 20+ hours of webhook debugging nightmares. Just connect Jira as trigger, set conditions for project/field changes, then push data wherever.

5

Your webhook visibility issue stems from using the v3 global endpoint, which creates system-level webhooks that are not displayed in the Jira administration interface. They exist outside the UI-specific webhooks.

Regarding delivery issues, assess your fieldIdsFilter first. The “summary” field typically has an internal ID like “summary,” but configurations can vary. Temporarily remove the fieldIdsFilter and perform a basic issue update to see if the webhook activates.

Another point to consider is the JQL filter syntax. Ensure that project names containing spaces or special characters are enclosed in quotes within the filter string. For example, use “project = ‘MYPROJECT’” if there are spaces in your project key.

Adding logging to your webhook endpoint can also help capture incoming requests, as delivery failures can occur for many reasons, including SSL certificate issues and response timeouts.

6

Atlassian handles REST API webhooks completely differently from admin interface ones. Your endpoint creates app-level webhooks that aren’t tied to specific projects - that’s why they don’t show up in your Jira admin dashboard. They’re managed purely through the API.

Your delivery failure is probably the fieldIdsFilter. “summary” isn’t the field ID Jira wants - it needs the internal system identifier. Try testing without fieldIdsFilter first to see if events fire, then add filters back gradually.

Also check that your webhook endpoint returns proper HTTP status codes when Jira hits it. The API might say webhook creation succeeded but fail silently during delivery if your endpoint doesn’t respond correctly.

7

This is normal behavior with REST API v3 webhook endpoints. Webhooks created through /rest/api/3/webhook are “dynamic” webhooks - they work differently from regular webhooks in the admin panel. They’re API-only and won’t show up in the UI.

For the payload issue, I’ve hit this before. Usually it’s authentication scope problems - your token might create webhooks but lack permissions to execute them. Also check that your webhook URL is publicly accessible and returns a 200 status when Jira tries to deliver.

I’d add some debugging to your endpoint first to see if requests are even reaching it. Jira’s webhook delivery can be delayed or fail silently if there are network issues or your endpoint responds too slowly.