Changes to API token functionality around Oct. 1, 2025?

[David Marshburn]

Were there any known changes to the API token functionality happening about Oct. 1, 2025, please?

We have an internally developed tool that, among other things, accesses Jira to provide status of issues.  We've been using API tokens in this tool for a couple of years, at least.

Starting Wednesday, Oct. 1, another user and I noticed that we are repeatedly presented with the following prompt by the tool.  We think this is the first time the behavior was noticed.  We both regenerated new tokens as part of testing; however, we keep being presented with this prompt.  The tool itself hasn't changed since Oct. 2024.

I do see that the token has been accessed

However, the tool still isn't pulling the statuses from the Jira issues and continues to prompt us to enter the token info.  Since the tool hasn't changed in some time, my guess or speculation is that something about how the tool should be accessing Jira has changed.  Are there API changes, for instance, that need to be incorporated in how our internal tool accesses Jira?  I'm looking for information to pass along to the maintainers of the tool.

Thanks!

[Charlie Misonne]

I'm not aware of related changes but I personally had to rework some scripts because of deprecated API endpoints.

have you tried calling the API endpoint manually (in your terminal or postman) with the same parameters and headers? Perhaps you'll find out that way.

[David Marshburn]

that's consistent with my guess -- deprecated API stuff.  Are you aware of any documentation of what has been deprecated when, please?

[Charlie Misonne]

Hi David

For me it was about this endpoint: https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issue-search/#api-rest-api-2-search-get

Being replaced with this one: https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issue-search/#api-rest-api-2-search-jql-get

The main difference is how the pagination works. The new endpoint uses a "nextpagetoken" parameter while the old one uses "startat".

This was announced almost a year ago and Atlassian started removing the endpoints in May this year.

@Mel Paisleyalso provided an interesting anwser

[David Marshburn]

Thanks for the specific endpoint pointers!  I'll pass those along!

[Mel Paisley]

In Dec 2024, Atlassian did start making API tokens expire by default (prior to then, they didn't expire) and in March this year, tokens created prior to Dec 2024 were also given an expiry date 12 months from that time.  

You can read more about tokens expiring at https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/. 

However, if you've checked the tokens are not expired - then the next thing to consider is that the API that your internally developed tool is using has potentially been deprecated and is now returning an error which your app is miss-interpreting as an authentication issue.

For changes to the Jira Cloud API - see the Jira Cloud Changelog 

For changes to the Confluence Cloud API - see the Confluence Cloud changelog 

There was a recent deprecation of the Jira Issue JQL Search API in September - it has been replaced with a new API that functions a little differently. See https://developer.atlassian.com/changelog/#CHANGE-2046

I hope this helps! 

[edited - initially provided wrong changelog link to JQL search API]

[David Marshburn]

Thanks for that!  

I'm pretty sure we're not having a token issue.  I had been using an old token, but I've generated a new token several times in the last week as part of testing.  Other users, as well.

I'll pass along the info about API changes.  I'm pretty sure we must be using a deprecated endpoint that, as you say, is being misinterpreted as an authentication issue.