apik
JOIN WAITLIST
TRACKING SHEET — 2 SOURCE(S)

Jira API changes

Atlassian Jira Cloud REST API. Signals: the Platform and Software (Agile) OpenAPI 3.0.1 specs. The Atlassian developer changelog is a JS SPA with no working RSS, so the specs are the reliable machine-readable signal.

LAST CHECKED
Jun 20, 2026
TRACKED SINCE
Jun 20, 2026
CHANGES / 90D
724
BREAKING / 90D
724
DETECTED CHANGES — MOST RECENT
  1. BREAKING Change Jun 20, 2026

    Get worklogs by issue id and worklog id

    - "version": "2024-09-30"
    + "version": "2025-06-01"
    - POST /v1/jira/charges
    + POST /v1/jira/payments  (auth scope changed)
  2. BREAKING Change Jun 20, 2026

    Set app property (Forge)

    - "version": "2024-09-30"
    + "version": "2025-06-01"
    - POST /v1/jira/charges
    + POST /v1/jira/payments  (auth scope changed)
  3. BREAKING Change Jun 20, 2026

    Get app property (Forge)

    - "version": "2024-09-30"
    + "version": "2025-06-01"
    - POST /v1/jira/charges
    + POST /v1/jira/payments  (auth scope changed)
  4. BREAKING Change Jun 20, 2026

    Delete app property (Forge)

    - "version": "2024-09-30"
    + "version": "2025-06-01"
    - POST /v1/jira/charges
    + POST /v1/jira/payments  (auth scope changed)
  5. BREAKING Change Jun 20, 2026

    Get app property keys (Forge)

    - "version": "2024-09-30"
    + "version": "2025-06-01"
    - POST /v1/jira/charges
    + POST /v1/jira/payments  (auth scope changed)

How to track Jira API changes

The Jira API evolves without warning — endpoints move, parameters change, auth scopes tighten and old fields get deprecated. apik.dev watches the public Jira API documentation for you: we scrape it on a schedule, diff every revision and grade each change as breaking or informational. Instead of re-reading the Jira changelog by hand, you get a clean, dated record of exactly what changed — and why it matters.

Get notified when the Jira API changes

Subscribe to Jira and apik pages you by email or webhook the moment a change is detected — with the full diff, a severity grade and a short migration summary. Filter to Jira breaking changes and deprecations only, so you hear about what will actually break your integration and nothing else.

FREQUENTLY ASKED — JIRA
How do I track Jira API changes?
apik.dev tracks the Jira API for you. We scrape the public Jira API documentation on a schedule, diff every revision and grade what changed — so you never have to re-read the Jira changelog by hand. Subscribe once and we monitor it continuously.
How do I get notified when the Jira API changes?
When apik detects a Jira API change, you're notified by email or webhook within hours — with the full diff, a severity grade (breaking vs. informational) and a short migration summary. You can choose to be alerted on breaking changes only.
What kinds of Jira API changes does apik detect?
Endpoint changes, base-URL changes, authentication and parameter changes, schema changes and deprecations. Every Jira API change is categorised and severity-graded so you can triage at a glance.
How often is the Jira API checked for changes?
apik re-checks the public Jira documentation on a daily schedule. The most recent check for Jira ran on Jun 20, 2026.
FIG. — GET PAGED NEXT TIME

Don't find out from a 500.

apik is in private development. Join the waitlist and we'll email you the moment Jira tracking goes live — full diffs, severity grading and migration summaries.

No spam — one email when we launch. Unsubscribe anytime.

Jira official docs ↗