Jira Cloud: GET /rest/api/3/search is gone, use POST /search/jql

TL;DR

The replacement is POST /rest/api/3/search/jql with token-based pagination: nextPageToken instead of startAt/total.

Steps

1. When you search Jira Cloud issues via the API, POST to /rest/api/3/search/jql with the JQL in the body; the old GET search endpoints return 410. Page with nextPageToken, not startAt, and stop when the token is missing. Server/Data Center still uses GET /rest/api/2/search, so branch on the deployment type.

When to use

You are seeing this: When you search Jira Cloud issues via the API, POST to /rest/api/3/search/jql with the JQL in the body; the old GET search endpoints return 410. Use this skill when you run into "Jira Cloud: GET /rest/api/3/search is gone, use POST /search/jql".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Jira API notes (statewave-connectors changelog): Atlassian removed GET /rest/api/2/search and /rest/api/3/search from Cloud (HTTP 410, CHANGE-2046). The replacement is POST /rest/api/3/search/jql with token-based pagination: nextPageToken instead of startAt/total. Pagination stops when the token is absent or a page is empty.

Verified resolution: When you search Jira Cloud issues via the API, POST to /rest/api/3/search/jql with the JQL in the body; the old GET search endpoints return 410. Page with nextPageToken, not startAt, and stop when the token is missing. Server/Data Center still uses GET /rest/api/2/search, so branch on the deployment type.

Source URL: https://github.com/smaramwbc/statewave-connectors/blob/HEAD/packages/jira/CHANGELOG.md