How to Test Jira Webhooks
Capture full Jira issue, sprint, and project event payloads during development — without waiting for production workflows to fire.
TL;DR: Get a free endpoint from requex.me, go to Jira System Settings → WebHooks (or Project Automation), add the URL, select the events, and create or update an issue. The full JSON payload appears in Requex instantly — no server required.
What Jira Sends
Jira webhooks send a rich JSON payload that includes the full issue object, the user who triggered the event, the changelog (what changed), and timestamps. The payloads are large — a single issue update can be several kilobytes. Seeing the real shape before building your handler is essential.
| Event | Trigger | Use Case |
|---|---|---|
jira:issue_created | New issue created | Auto-assign, notifications, CRM sync |
jira:issue_updated | Issue fields, status, or assignee changed | Status sync, deployment gates |
jira:issue_deleted | Issue deleted | Audit logging, external sync cleanup |
sprint_created | New sprint created in a board | Capacity planning automation |
sprint_started | Sprint starts | Team notifications, metric snapshots |
project_created | New Jira project created | Provisioning, access management |
Step 1 — Generate a Requex Endpoint
Open requex.me and copy your unique URL:
https://requex.me/hook/a1b2c3d4-e5f6-7890-abcd-ef1234567890
Step 2 — Configure Jira Webhook
Jira offers two places to set up webhooks depending on your version and use case:
Jira Cloud — System WebHooks (Admin)
- Go to Jira Settings (gear icon) → System → WebHooks.
- Click Create a WebHook.
- Paste your Requex URL into the URL field.
- Select the events: Issue events, Project events, and Sprint events are the most used.
- Optionally add a JQL filter to limit events to a specific project (e.g.,
project = MYPROJECT). - Click Create.
Jira Cloud — Project Automation
- Go to your project → Project Settings → Automation.
- Create a new rule with a trigger (e.g., "Issue updated").
- Add a Send web request action and paste your Requex URL.
- This approach works for projects where you don't have Jira admin access.
Step 3 — Trigger a Test Event
Create a new issue in any project covered by your webhook. Go to Create Issue, fill in the summary, and save. The jira:issue_created event fires immediately and should appear in Requex within a few seconds.
To test jira:issue_updated, change the status of the issue you just created — drag it to "In Progress" on the board. Each status transition fires a separate event with a full changelog array.
Step 4 — Inspect the Payload
Jira payloads are rich and deeply nested. Here is a condensed example of an issue_updated event:
{
"timestamp": 1712345678901,
"webhookEvent": "jira:issue_updated",
"issue_event_type_name": "issue_generic",
"user": {
"accountId": "5b1234abc123",
"displayName": "Jane Smith",
"emailAddress": "jane@example.com"
},
"issue": {
"id": "10042",
"key": "PROJ-42",
"fields": {
"summary": "Fix login redirect bug",
"status": { "name": "In Progress" },
"assignee": { "displayName": "Jane Smith" },
"priority": { "name": "High" },
"issuetype": { "name": "Bug" }
}
},
"changelog": {
"id": "12345",
"items": [
{
"field": "status",
"fromString": "To Do",
"toString": "In Progress"
}
]
}
}The changelog.items array is what your handler should inspect to determine what actually changed. A single update can contain multiple changelog items if several fields changed simultaneously.
Jira-Specific Behaviour
X-Atlassian-Token header
Jira sets X-Atlassian-Token: no-check on every request. This is a remnant of Jira's CSRF protection system — it signals that CSRF validation should be skipped. Your endpoint can ignore it safely.
No signature by default (Jira Cloud)
Jira Cloud webhooks do not include an HMAC signature header by default. If you need to secure your endpoint, put it behind a secret path or use the Requex authentication settings to require a custom header or token from Jira's Automation "Send web request" action.
JQL filtering reduces noise
Without a JQL filter, your webhook receives events from every project in the instance. Add project = YOUR_PROJECT_KEY to the JQL field to limit events during development.
Common Issues
| Problem | Cause | Fix |
|---|---|---|
| No events arriving | Webhook system settings require admin access | Use Project Automation instead, or ask your Jira admin to create the system webhook |
| Too many events flooding the endpoint | No JQL filter applied | Add a JQL clause to restrict to your project or issue type |
| Payload missing custom fields | Custom fields use internal IDs not names | Use the Jira API to map customfield_10001 IDs to human-readable names |
Test Jira Webhooks Free
Capture full Jira issue payloads and inspect every field in the changelog. No signup required.
Open Requex →Related guides
Start Testing Webhooks Now
Generate your unique URL and test webhooks instantly. Free, no signup.
Open Webhook Tester →