nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

API for rotating API Tokens and checking expiration date

Victor La

Since API tokens have a maximum lifetime of 365 days, we’d like to incorporate token rotation into our credential-rotation process and renew tokens before they expire.

Is there an API available to rotate these API tokens programmatically?

Additionally, for reporting and monitoring purposes, is there an API or other method to retrieve a token’s expiration date? Tokens may be created by different users, including service accounts, and we may not know their creation dates, making it difficult to determine when they will expire.

Accepted answers

Arkadiusz Wroblewski

Hello @Victor La

List/Read API Tokens Definitely so Retrieve Expiration date should be doable.

curl --request GET \ --url 'https://api.atlassian.com/admin/api-access/v1/orgs/{orgId}/api-tokens' \

Rotate - I don´t think so at the moment.

The API Access REST API

Best,

Arek🤠

All comments

Arkadiusz Wroblewski

Hello @Victor La

List/Read API Tokens Definitely so Retrieve Expiration date should be doable.

curl --request GET \ --url 'https://api.atlassian.com/admin/api-access/v1/orgs/{orgId}/api-tokens' \

Rotate - I don´t think so at the moment.

The API Access REST API

Best,

Arek🤠

Victor La

@Arkadiusz Wroblewski, thank you for getting back to me! I have a follow up question.

Based on the documentation, it looks like this endpoint requires an organization-level API key rather than an API token? I assume there isn't a way with the API token?

Trudy P Claspill

Hello @Victor La

In this case "key" and "token" are essentially the same thing. The difference is that the process needs Organization Admin level access to see all the API token names and expiration dates across all accounts in the Organization. The only way to get a "token" that has Organization Admin level access is to generate it from the Admin Hub > Organization Settings > API Keys. That can be done only by an Organization Admin.

Screenshot 2026-08-26 at 6.07.14 PM.png

Arkadiusz Wroblewski

@Victor La

Yes, @Trudy P Claspill elaborated on that a little.

Look at it from this perspective: generating API tokens sits under user settings because they are Personal (Admins can Restrict who can create them or revoke them), while the overview and management of keys/tokens sits under organization administration.

For many administrative automation tasks, you need an organization-level API key, simply because the relevant API endpoints belong to the organization administration layer.

Arkadiusz Wroblewski

Nothing to thank us for. We are here to help each other.🫂🤠

I recommend voting on this issue

https://jira.atlassian.com/browse/ID-8077

With your own internal IT, we can't help. In my opinion, there will be much fewer Questions here if users and Admins communicate more and clearer.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud