Jira and Confluence Cloud REST APIs
GET /rest/api/3/search endpoint removal
Deprecated, no dateSubscribe to Jira and Confluence Cloud REST APIsShare
Jira and Confluence Cloud REST APIs deprecated the GET /rest/api/3/search endpoint without a shutdown date, noting that the endpoint is currently being removed. Once removed, requests to this endpoint will fail.
Calls it hits
GET /rest/api/3/search
What to use instead of these calls
Call GET /rest/api/3/search/jql instead. The replacement endpoint pages with nextPageToken instead of startAt and returns only ids unless fields are requested.
In Jira and Confluence Cloud REST APIs's words
Endpoint is currently being removed.
Facts
- API
- Jira and Confluence Cloud REST APIs
*.atlassian.net - Kind
- Endpoint removal
- Announced
- October 31, 2024
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Jira and Confluence Cloud REST APIs's own pages
Questions
When does this change take effect?
Jira and Confluence Cloud REST APIs deprecated GET /rest/api/3/search without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Jira and Confluence Cloud REST APIs 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 Jira and Confluence Cloud REST APIs 10
-
GET /rest/api/3/workflow/searchEndpoint removal Stopped working -
GET /rest/api/3/field/{id}/context/defaultValueEndpoint removal Stopped working -
PUT /rest/api/3/field/{id}/context/defaultValueEndpoint removal Stopped working -
No date
GET /rest/api/2/searchEndpoint removal Deprecated, no date -
No date
GET /rest/api/3/issue/createmetaEndpoint removal Deprecated, no date -
No date
GET /rest/api/latest/searchEndpoint removal Deprecated, no date -
No date
POST /rest/api/2/expression/evalEndpoint removal Deprecated, no date -
No date
POST /rest/api/2/searchEndpoint removal Deprecated, no date -
No date
POST /rest/api/3/expression/evalEndpoint removal Deprecated, no date -
No date
POST /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.