Clarification on Deprecation of /rest/api/3/search and /rest/api/2/search

[sarvesh]

Hi,

I noticed that both the /rest/api/2/search and /rest/api/3/search endpoints are listed as deprecated in the official documentation. However, when I test these endpoints, they are still functioning as expected.

Could you please confirm if there is a timeline for the full deprecation of these endpoints? If so, are there any new endpoints or methods we should be using instead? Additionally, is there any official guidance on transitioning away from these deprecated endpoints?

Thank you,

[Trudy Claspill]

Hello @sarvesh 

Welcome to the Atlassian community.

The API documentation includes alternative API endpoints.

[Vishal Biyani]

but is there a date when the deprecated APIs will stop working?

[Trudy Claspill]

You can find deprecation notices for the API with target dates here:

https://developer.atlassian.com/changelog/#atlassian-developer-changelog

For the issue search endpoints specifically:

https://developer.atlassian.com/changelog/#CHANGE-2046

[Sebastien Brion]

@Trudy Claspill do we know how long the deprecation is being extended?

The post you indicated says "May 1st, 2025" but the endpoint are still up (which is good, since the jira python library does not out-of-the-box support the new endpoints yet).

[Trudy Claspill]

@Sebastien Brion 

I have no information on deprecation extensions.

If you have a paid subscription, you or your admins could open a support case directly with Atlassian to ask.

https://support.atlassian.com/contact/#/