Atlassian Cloud API
GET /ex/jira/{id}/rest/api/2/search endpoint removal
Deprecated, no dateSubscribe to Atlassian Cloud APIShare
Atlassian Cloud API deprecated GET /ex/jira/{id}/rest/api/2/search without a shutdown date, noting that the endpoint is currently being removed. Once removed, requests to this endpoint will fail.
Calls it hits
GET /ex/jira/{id}/rest/api/2/search
What to use instead of these calls
Call GET /ex/jira/{}/rest/api/2/search/jql instead. This replacement pages with nextPageToken instead of startAt and returns only ids unless fields are requested.
In Atlassian Cloud API's words
Endpoint is currently being removed.
Facts
- API
- Atlassian Cloud API
api.atlassian.com - Kind
- Endpoint removal
- Announced
- October 31, 2024
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Atlassian Cloud API's own pages
Questions
When does this change take effect?
Atlassian Cloud API deprecated GET /ex/jira/{id}/rest/api/2/search without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Atlassian Cloud API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Atlassian Cloud API 4
-
No date
GET /ex/jira/{id}/rest/api/3/searchEndpoint removal Deprecated, no date -
No date
POST /ex/jira/{id}/rest/api/2/searchEndpoint removal Deprecated, no date -
No date
POST /ex/jira/{id}/rest/api/3/expression/evalEndpoint removal Deprecated, no date -
No date
POST /ex/jira/{id}/rest/api/3/searchEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.