ZoomInfo Invalid Credentials Error in Enrichment Column Issue

Jon Y. · 2026-01-30T20:45:07.420Z

Is anyone else having issues with ZoomInfo? I suddenly started getting "Invalid Credentials" error in the enrichment column. I have tried refreshing my ZoomInfo connection login also. I am not sure if this is a Clay issue or a ZoomInfo issue.

ZoomInfo Invalid Credentials Error in Enrichment Column Issue | Clay

Clay Support
APP
·
·
The "Invalid Credentials" error with ZoomInfo usually happens for a few reasons:
• Your email or password is incorrect
• Your ZoomInfo account doesn't have API access enabled
• You're using SSO (Single Sign-On), which isn't supported for API [1]
Since you've already tried refreshing your connection, I'd recommend reaching out to ZoomInfo support directly to confirm your account has API access and to get it unblocked if needed. [2]
Before we escalate this further, try using Sculptor (top-right corner) - paste your error message there and it might suggest additional fixes. Let me know if Sculptor helps or not!
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you still need help resolving the ZoomInfo "Invalid Credentials" error, I’m here to assist. Would you like to provide more details about what you’ve tried or any other issues you’re encountering?
Jon Y.
·
·
I have logged into ZoomInfo successfully with my username and password.
We are not using SSO
I have ensured that API use has been turned on for my account.
Clay Support
APP
·
·
Since you've confirmed your credentials work, API access is enabled, and you're not using SSO, this sounds like it might be a temporary issue on ZoomInfo's end or with the API connection itself.
Try disconnecting and reconnecting your ZoomInfo account completely in Clay:
1. Go to Settings → Connected accounts
2. Find ZoomInfo and disconnect it
3. Add the account again with fresh authentication
If that doesn't work, you'll likely need to contact ZoomInfo support directly since the issue appears to be on their API side rather than with Clay. [1]
Before we go further though, have you tried using Sculptor yet? Paste your exact error message there - it might catch something we're missing.
Jon Y.
·
·
yes i tried using Sculptor and it said it may be faster to speak with a human instead.
Clay Support
APP
·
·
Got it — I’m connecting you to a human teammate now.
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)
Natalie (.
·
·
Hi Jon, sorry to hear this is happening! Do you mind sending the link (url) to the table so we can take a look? We can help you look at the logs from there. Thanks!
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!
Jon Y.
·
·
Natalie (. Sorry for missing this message. Here is the Clay table: https://app.clay.com/workspaces/572542/workbooks/wb_0t8eqlhgTuDEYwU4vtm/tables/t_0t8eqlv4H2G48qcdHa3/views/gv_0t8eqlv4A7pTzW4BrH4
Natalie (.
·
·
No worries, thanks Jon! Yep in the logs I see "You do not have access to this endpoint. Please contact your ZoomInfo Account Manager for purchasing options" but that's strange to me, because we can clearly see it working for other rows! I'm going to put together my notes on this, and escalate it so our engineering team can take a look!
Jon Y.
·
·
I am looking at another Error message that talks about updating the API token, but I have not seen a place in Clay where the API token can be updated for ZoomInfo.
Natalie (.
·
·
Thanks Jon - if you go to Settings by clicking on your profile picture --> Connections, you can delete and/or add a new API token by clicking "Add connection":
Jon Y.
·
·
but I dont see anywhere to enter a API token key. Only to login or "Reconnect"

17 comments