Status on the deprication of "POST /rest/api/2|3|latest/search"

[Abhishek Chauhan]

https://developer.atlassian.com/changelog/?utm_source=chatgpt.com#CHANGE-2046

While calling the "POST /rest/api/2/search" on few of the Jira cloud instance, it is returning 410 that API is deprecated. However, when calling the same API on the different jira cloud instance, it is working. 

I would like to understand how the versions are rolled out in the Jira cloud and why this could happen that one Jira instance leads to an error and on other one it works fine.

[Gor Greyan]

Hi @Abhishek Chauhan

Welcome to the Atlassian Community!

Atlassian announced deprecation of the classic search endpoints (e.g., …/rest/api/2/search and …/rest/api/3/search) in favor of the new “Enhanced JQL” search APIs. As removal rolls out, some sites now return 410 Gone while others still accept the old calls.

You can use /rest/api/3/search/jql (GET or POST). These are the Atlassian-recommended replacements for the old /search endpoints.

You can also check the following article in Atlassian Community - https://community.atlassian.com/forums/Jira-questions/Deprecation-of-JQL-search-endpoints-rest-api-3-search/qaq-p/2859040?utm_source=chatgpt.com

And this one in Atlassian Developer Community - https://community.developer.atlassian.com/t/rest-api-3-search-jql-isnt-returning-results-i-know-my-jql-should-do/94630?utm_source=chatgpt.com