API key created but not showing in /api-keys gui

Hi all,
I’ve created 3 API keys of which I am successfully using one, so that confirms that they exist. However they are not being listed in https://platform.openai.com/api-keys. The page continues to say “You currently do not have any API keys”

Without them being listed I am unable to manage them such as ‘delete’

Steps to reproduce:

  1. create new key
  2. newly created key not shown in gui but useable in api

I have billing setup and am being charged as expected
I have tried the following:

  • clear browser cache, incognito browser, other browser - same issue
  • called the API using different models - that hasn’t fixed it

Anyone else seen this and fixed?
Thx

1 Like

Issue resolved in the background. Maybe this post triggered the fix :woman_shrugging:

Hello, because the issue was solved I would appreciate if you would mark your post as the solution. :smiley:

1 Like

Hello, i have same error. It seems not been solved yet.

We’re running into this issue as well.

Is there any way to manage keys outside of this (broken) UI?

We’ve provisioned keys that we can no longer see, and therefore can no longer manage :worried:

I’ve come across a similar issue. I can’t see all my created keys, but I use them. I have only one organization for my account, I’ve tried different browsers also, tried to clean all cache and it didn’t help. The problem isn’t solved yet.

I have the same problem. 2 keys, both are used somewhere, but I see only 1 in the dashboard.

The problem is that the invisible one is used by some application I created long ago. I don’t remember in which. And I can’t even deactivate the key.

Are you logged in as the owner of the project and have you selected the right project?

Project selection top left

Full list of owners can be found here.

I can confirm this is an ongoing issue. I have selected the right project, I am the owner, and the API key I am using is not listed. I am still using the key and being billed for it, so it’s clearly marked somewhere that it’s mine.

thank you for the update, I was experiencing the same thing