Troubleshooting Zoominfo API Key Error: Adding Authorization in Table Threads

Can someone please help me with adding my Zoominfo API key- Im getting an error around authorization - adding my table in threads.

11 comments

Landon M.
·
·
https://app.clay.com/workspaces/42478/tables/t_hHTugTYVoKxz/views/gv_kMdE96DkbLEq
Landon M.
·
·
Arturo O. can you tag that developer you were talking about so we can hop on screen share after Christmas break.
Arturo O.
·
·
Sorry for the delay, Landon! Will look into it. I tried taking another stab at it but the error is just saying that the authentication field has unsupported characters(?). Ill tag Maggie W. ahead of time but we’ll check it out as soon as available 😃
Landon M.
·
·
Thank you!
Maggie W.
·
·
Hi Landon M., apologies for delay here. The API key you had in the field had unnecessary breakline characters (probably from a bad copy paste) which seems to be what was causing the unsupported characters error. I resolved that issue but now that same enrichment shows an Unauthrized request error, indicating that the API key is not authorized to perform the request. can you double check and confirm your API key here?
Landon M.
·
·
Maggie W. I had my team generate new token and they copy and paste and sent to me on slack- I then copy and pasted it into clay but still getting error- what am I doing wrong here?
Landon M.
·
·
https://app.clay.com/workspaces/42478/tables/t_hHTugTYVoKxz/views/gv_kMdE96DkbLEq
Clay Team
APP
·
·
Hey Landon, also checking on this one. I do see it still returns unauthorized, any chance ZI's teams can check if your API token is properly enabled?
Landon M.
·
·
This is what they said..
Landon M.
·
·
oh should I try inluding the begin private key-- and --End private key--
Maggie W.
·
·
Hi Landon M., without seeing how or where the key is being generated from, its difficult for me to debug this or tell what you are doing wrong. the breaklines from the api key being very long was something i identified originally when trying to solve this, but after fixing that there was still an issue of the API key having unsupported characters. now that seems to be resolved and whatever api key youre using is just not authorized to perform the operation youre attempting with this HTTP API request. That means that either your API key is actually not authorized and you do not have these permissions, or the api key has been accidentally modified during the copy/paste into the application