Is Atlassian deprecating v2 APIs entirely?

[Samrat Dutta]

While Atlassian has not fully phased out the Jira v2 APIs yet, some endpoints (such as Search and JQL) have already been deprecated.

I'd like to confirm whether this API is expected to remain supported in the near term. If deprecation is planned, it would be helpful to understand the timeline so we have sufficient runway to prepare and avoid any surprises for our customers.

[Artem Nek]

Hi Samrat

Short answer: no — Atlassian isn't retiring the v2 (or v3) Jira platform REST
API as a whole. Both remain supported; v3 is just the ADF-aware twin of v2,
not a replacement that deprecates it.

What got deprecated was a specific set of endpoints — not a version. This was
announced back in October 2024:

• GET/POST /rest/api/{2|3|latest}/search
• POST /rest/api/{2|3|latest}/search/id
• POST /rest/api/{2|3|latest}/expression/eval

Replacements:
• Search → POST /rest/api/{2|3|latest}/search/jql
• Expression eval → POST /rest/api/3/expression/evaluate

This one's already done, not upcoming: those endpoints went through their
sunset over 2025 and the old /search now returns 410 Gone on Cloud. So if
something is still pointed at them today, it's already broken rather than
"about to break" — migrating to /search/jql isn't optional anymore.

Two behavioural changes that catch people out on the new endpoint:
• queries are bounded — you must pass an explicit `fields` list (and
maxResults); no more implicit "return everything"
• pagination is cursor-based via `nextPageToken`, not startAt/total

For your underlying question about runway: there's no blanket v2/v3 retirement
to plan around. Deprecations are handled per-endpoint, each with its own
notice
period, and they all land in the Jira Cloud platform changelog — watching that
is the cleanest way to catch anything before it affects customers.

• How to run JQL search on the new endpoint (fields + nextPageToken
examples)
• Jira Cloud platform changelog:
https://developer.atlassian.com/cloud/jira/platform/changelog/

(Aside: if "v2" ever comes up in a Confluence context, that's the opposite
case
— there it's v1 being retired in favour of v2, so v2 is the one to be on.)