Hey Team, Clay APi key is not working, I created a new APi key to use Lookup records. It worked but after 1 hour, it didn't work. It's happening for third time. How to fix this?
This sounds like an API key configuration issue. Here's how to fix it:
1. Check your API key location: Go to Settings > Your Profile > API Key section and copy the correct key
2. Update integration settings: Add the API key to your integration account in Clay under the Integrations section and save changes [1]
3. If compromised, regenerate: Since this keeps happening, your key might be compromised. You can regenerate it immediately through the API Key section [2]
The intermittent failure pattern suggests the key isn't properly saved in your integration settings or needs regeneration for security.
Is that what you were looking for?
I regenrated the key and added it twice, still facing the same issue SHowing this error: {"type":"Unauthorized","message":"You must be logged in","details":null}
The "You must be logged in" error suggests the API key isn't being recognized properly. Here's what to check:
Double-check your integration setup:
Go to Settings → Integrations section in Clay
Find your integration and make sure the API key is saved there (not just copied) [1]
Verify the correct API key location:
Get your key from Settings → Your Profile → API Key section
Make sure you're copying the full key without extra spaces
Since you mentioned JSON formatting issues earlier, can you copy and paste the exact request you're making (including headers) so I can help troubleshoot the authentication setup?
I'm using Lookup Integration to check records on diff tables
For the "You must be logged in" error with Lookup integrations, the issue is likely with how your API key is connected in the integration settings.
Go to Settings > Connections and search for "Clay" - make sure your API key is properly linked there.
Also verify you're getting your API key from the right place: Settings > Account > API Key (not just your profile section). [1]
The key needs to be saved in the Connections section, not just copied - that's usually what causes the authentication to fail after working initially. [2]
Did that answer your question?
If you still need help resolving the API key issue, I’m here to assist further. Would you like to provide more details about your integration setup or the exact steps you’re taking?
