Trying to create our 1st API key but nothing happeningT

[Mina Abdelmalek]

Hello,

We subscribed to the free version of JIRA for our PoC and trying to create an API key to connect SAP cloud ALM but nothing happens!

After choosing the name, scope and by clicking create API Key no further actions happen, is this a bug or am I missing something?

I'm the organization admin

Thank you 

Mina

[Trudy Claspill]

Hello @Mina Abdelmalek 

Welcome to the Atlassian community.

API tokens can be generated by individual users, by Organization Admins for Service Accounts, and by Organization Admins for access to Organization-management APIs. Which were you trying to generate?

Can you provide a link to the documentation with the steps you are following? Or if you are not using documentation, provide a list of the steps you executed?

[Trudy Claspill]

@Mina Abdelmalek 

Here is a link to the relevant documentation:

https://support.atlassian.com/organization-administration/docs/manage-an-organization-with-the-admin-apis/

Let us know if you encounter difficulties following that guide.

[Mina Abdelmalek]

Hi 

I have been already following the steps mentioned in the documentation, after selecting a name/expiry/scope & by reviewing the API key details clicking on create doesn't proceed with the creation.

Tried with scope or without and many times still same issue!

Nothing happen after clicking on create.

 

Thanks,

Mina

[Trudy Claspill]

Thank you for that information.

Do you see an change in the UI button as you click it, as often happens with UI buttons to indicate the click/press was recognized?

Do other Organization Admins have the same experience?

Have you tried any of the following?

1. Clear your browser cache and retry
2. Use a private browser window and retry.
3. Use a different browser application.

I have tried the same in my own Free environment in a Chrome Incognito window (which is how I usually work). After clicking the Create API Key button I got an "in progress" spinner for a few seconds and then the screen changed to display the new api key and a Done button. It was successful with and without Scopes. So this is not a full outage of the functionality across all customers, at least.

[Mina Abdelmalek]

I tried both chrome and edge Incognito modes and same issue

For me it spins for a second and then screen stays on the same one I shared, it doesn't move to the "in progress" state

I'm the only org. admin for this account now.

[Trudy Claspill]

I don't see any active incidents on Atlassian's status page that would relate to this.

https://status.atlassian.com/

I'm going to flag your post here to raise it to the Atlassian of Atlassian team members who can investigate from the backend. They should respond within 2 business days.

[Mina Abdelmalek]

Thank you @Trudy Claspill that would be appreciated

[Matthew John Gardner]

Hello Atlassian Support,

I am in addition encountering a failure in the Atlassian Admin portal when attempting to use the API Keys functionality.

The issue appears to originate from Atlassian’s frontend/runtime environment and backend API services rather than from the client browser or local environment.

Observed behaviour:

• Requests to the API Keys endpoint fail with HTTP 500 responses.
• The frontend logs multiple runtime dependency/version conflicts:
  “Multiple versions of FeatureGateClients found on the current page”
  including mismatched versions such as:
  bound version: 4.26.5
  loading version: 5.25.1
  loading version: 0.0.0-use.local
• Apollo GraphQL runtime errors are also present:
  “either ensure all objects of type Organization have an ID or a custom merge function”
  The page is additionally generating extensive frontend asset and source-map failures across multiple Atlassian bundles.

The issue persists despite:

• hard refreshes,
• cache clearing,
• private browsing sessions,
• and browser changes.
• This strongly suggests a problem with Atlassian’s deployed frontend bundles, cache invalidation/versioning, or backend API services associated with admin.atlassian.com.

Please investigate:

• the API Access service returning HTTP 500,
• frontend bundle/version mismatches,
• GraphQL cache/runtime configuration issues,
• and any recent deployments affecting the Admin/API Keys experience.
• If available, please also review backend traces associated with the failed POST requests to the API Keys endpoint.

Thank you.

[Mina Abdelmalek]

Thank you both @Trudy Claspill & @Joseph Chung Yin  for replying

I was generating Organization-management API from Admin->Organization Settings -> API Keys

Unfortunately couldn't find a clear documentation from Atlassian side

[Anastasiia Dimnych]

Hi @Mina Abdelmalek,

Apologies for delay on our end! I created a ticket with the support team on your behalf. You will be receiving communication via the ticket JST-1312529.

Best,

Anastasiia

[Mina Abdelmalek]

Thank You @Anastasiia Dimnych 

[Mina Abdelmalek]

This is still not answered and remains as an open issue

Anyone from support team able to help us out please??

[Matthew John Gardner]

I have the same issue, can't create keys, its just stuck. 

[Joseph Chung Yin]

@Mina Abdelmalek 

I agreed with @Trudy Claspill as we need further information from you to better understand your issue that you are facing, so we can provide further assistance.

Best, Joseph