OpenAI API Key Issues Across Multiple Accounts

Jaimin B. · 2025-11-13 01:39:35.829038+00

My openAI API key is not working. Seeing this across multiple accounts with multiple OpenAI keys.

OpenAI API Key Issues Across Multiple Accounts | Clay

15 comments

· Sorted by Oldest

Clay Support
APP
·
·
The "Could not verify the OpenAI API key" error typically indicates an incorrect API key or insufficient tier access.
First, verify your API key at OpenAI API Keys and update it in Clay.
If the key is correct, check your OpenAI usage tier at OpenAI API Usage Limits. Clay requires 30,000 TPM for ChatGPT columns and 450,000 TPM for Claygent - free tier and Tier 1 won't work.
To update your API key in Clay: go to your profile picture → Settings → Connections → find OpenAI integration → click "..." → Edit → update the key.
You'll likely need to upgrade to Tier 2 or higher for reliable performance.
Clay Support
APP
·
·
Is that what you were looking for?
Jaimin B.
·
·
I changed the API key and I'm on Tier 3 so it doesn';t seem like the issue. Also, it was working totally fine until a couple days ago.
Clay Support
APP
·
·
Since you've updated your API key and are on Tier 3, let's test the connection to verify it's working properly.
Go to Settings → Connections → find your OpenAI integration → click "..." → Test Connection to confirm the key is functioning.
If the test fails, click into the specific error cell to see more detailed error information. This will help identify if there's a specific issue with the API key verification or another underlying problem.
Clay Support
APP
·
·
Did that answer your question?
Jaimin B.
·
·
It came out as success
Clay Support
APP
·
·
Since your connection test passed but you're still seeing the API key verification error, this suggests the issue may be intermittent or specific to certain operations.
Try clicking into the specific error cell where you're seeing the "Could not verify" message to get more detailed error information. This will help identify if there's a specific issue with certain API calls or rate limits being hit during actual usage versus the connection test.
Clay Support
APP
·
·
Did that answer your question?
Jaimin B.
·
·
No.
Clay Support
APP
·
·
I understand this is frustrating, so I’m routing you to one of our human agents who can assist you further.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon!
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
image.png(93 kB)
Jaimin B.
·
·
https://app.clay.com/workspaces/11191/workbooks/wb_0t5ld0bYe5XXuRCcsZS/tables/t_0t5ldlbuZgeSYGuZd5s/views/gv_0t5ldlcHaSo8gxHgGKH
Michael K.
·
·
it seems like the issue might be with GPT 5 models — I’m getting the same error with them but not with 4 models.
Kashif J.
·
·
Hi Jaimin,
Thank you for getting in touch. I've reviewed your table and successfully tested 10 rows in the "Architecture Firm" column using both the gpt-4 and gpt-5 models, so the functionality is working as expected.
I did notice the warning message appearing next to your API key, as shown in your image. Whilst the rows ran successfully despite this, I'm going to investigate why the warning is displaying further.
Could you let me know whether you're now able to run rows with the gpt-5 model on your end (and additionally if you happened to change something on the OpenAI side of things to get this to work now)?
Please get in touch if you have any other questions or if the issue persists.
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.
Still need help here? Reply back and someone will jump back in.
Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!

Clay Support
APP
·
·
The "Could not verify the OpenAI API key" error typically indicates an incorrect API key or insufficient tier access.
First, verify your API key at OpenAI API Keys and update it in Clay.
If the key is correct, check your OpenAI usage tier at OpenAI API Usage Limits. Clay requires 30,000 TPM for ChatGPT columns and 450,000 TPM for Claygent - free tier and Tier 1 won't work.
To update your API key in Clay: go to your profile picture → Settings → Connections → find OpenAI integration → click "..." → Edit → update the key.
You'll likely need to upgrade to Tier 2 or higher for reliable performance.
Clay Support
APP
·
·
Is that what you were looking for?
Jaimin B.
·
·
I changed the API key and I'm on Tier 3 so it doesn';t seem like the issue. Also, it was working totally fine until a couple days ago.
Clay Support
APP
·
·
Since you've updated your API key and are on Tier 3, let's test the connection to verify it's working properly.
Go to Settings → Connections → find your OpenAI integration → click "..." → Test Connection to confirm the key is functioning.
If the test fails, click into the specific error cell to see more detailed error information. This will help identify if there's a specific issue with the API key verification or another underlying problem.
Clay Support
APP
·
·
Did that answer your question?
Jaimin B.
·
·
It came out as success
Clay Support
APP
·
·
Since your connection test passed but you're still seeing the API key verification error, this suggests the issue may be intermittent or specific to certain operations.
Try clicking into the specific error cell where you're seeing the "Could not verify" message to get more detailed error information. This will help identify if there's a specific issue with certain API calls or rate limits being hit during actual usage versus the connection test.
Clay Support
APP
·
·
Did that answer your question?
Jaimin B.
·
·
No.
Clay Support
APP
·
·
I understand this is frustrating, so I’m routing you to one of our human agents who can assist you further.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon!
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
image.png(93 kB)
Jaimin B.
·
·
https://app.clay.com/workspaces/11191/workbooks/wb_0t5ld0bYe5XXuRCcsZS/tables/t_0t5ldlbuZgeSYGuZd5s/views/gv_0t5ldlcHaSo8gxHgGKH
Michael K.
·
·
it seems like the issue might be with GPT 5 models — I’m getting the same error with them but not with 4 models.
Kashif J.
·
·
Hi Jaimin,
Thank you for getting in touch. I've reviewed your table and successfully tested 10 rows in the "Architecture Firm" column using both the gpt-4 and gpt-5 models, so the functionality is working as expected.
I did notice the warning message appearing next to your API key, as shown in your image. Whilst the rows ran successfully despite this, I'm going to investigate why the warning is displaying further.
Could you let me know whether you're now able to run rows with the gpt-5 model on your end (and additionally if you happened to change something on the OpenAI side of things to get this to work now)?
Please get in touch if you have any other questions or if the issue persists.
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.
Still need help here? Reply back and someone will jump back in.
Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!