Timelines to understand when #CHANGE-2046 would be available to all instances

[Parag Dhake]

We are encountering the following issue with one of our Jira Service Management (JSM) instances:

 { "errorMessages": [ "The requested API has been removed. Please migrate to the /rest/api/3/search/jql API. A full migration guideline is available at https://developer.atlassian.com/changelog/#CHANGE-2046" ], "errors": {} }

However, when using the same endpoint in another JSM instance, we do not face this issue — it works as expected there.

Could you please confirm the timeline for when this API change will be enforced across all Jira Service Management instances?

LogicMonitor integrates with Jira, and the removal of the old API endpoint has already started impacting some of our existing customers. We’d like to understand when this change will be fully rolled out so we can plan and communicate accordingly.

[Chitra Nagdeo · Accepted solution]

Hey @Parag Dhake ,

Welcome to Atlassian community!

Jira Cloud REST API v2 Deprecation Timeline

• 2024-10-31: Atlassian announced the deprecation of v2 and published the migration guide (Atlassian developer changelog).
• 2025-05-01: Deprecation period ends. v2 is no longer supported for new development.
• 2025-05-05 to 2025-07-31: Atlassian rolls out a hybrid solution, Old endpoints still work but may have eventual consistency and performance changes.
• 2025-08-01 to 2025-10-31: Full shutdown phase. Atlassian will progressively disable v2 endpoints for all customers. By October 31, 2025, v2 endpoints will be fully retired and stop responding.

Below are the list of API which is changing

GET /rest/api/3/search --> GET /rest/api/3/search/jql

POST /rest/api/3/search --> POST /rest/api/3/search/jql

POST /rest/api/3/search/id --> POST /rest/api/3/search/jql

POST /rest/api/3/expression/eval --> POST /rest/api/3/expression/evaluate

I hope this helps! 

Regards
Chitra Nagdeo

[Marc - Devoteam]

Hi @Parag Dhake 

You should switch to the new endpoint ASAP, the other endpoint is phased out over time.

There is no set timeline for this, this API option is actively being disabled on every Cloud instance.

Expect this to be gone, before the end of the year, as the article stated it should have been removed already before the 1st of May 2025