Happened to us quite a few times now but keep getting 'Missing authentication' errors in cells that we have not changed and worked perfectly before. Same thing happened for multiple different HTTP API call columns, not just one specific one.
This error typically occurs due to authentication issues with your HTTP API calls. Here are a few key things to check:
1. Verify your Authorization header is properly set up:
• Make sure you have included the Authorization header in your request
• Check that the token format is correct (e.g., Authorization: Bearer <token> )
2. Double-check your JWT token formatting:
• Ensure the JWT is correctly identified and formatted
• Verify the token hasn't expired
3. Review your request headers:
• Confirm all required headers are present
• Check that the Content-Type header is set to application/json
Try performing a hard refresh (Cmd/Ctrl + Shift + R) of your browser, as this can sometimes resolve authentication-related issues.
Did that answer your question?
Looks like you're still looking for help.
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!
Hey Seb, Sorry for that I'd need a bit more information to help troubleshoot this effectively. Could you share: 1. When did you first notice this issue? 2. Did you make any recent changes to your HTTP API before this started happening? (Other than the Auth) 3. Are you able to check if your API keys or tokens are still valid in the services you're connecting to? 4. Does this happen in all tables? If so can you show me other tables? This will help us pinpoint the exact cause and get it resolved quickly. Us and the engineering team would need these details to investigate properly. Let me know
in the last week
no changes
the api keys are still valid as they work outside of clay
it happens in all tables for entirely different api calls too
if i duplicate the column, it still doesn’t work. But, if i create a new http api column and set it up identically it does work
Hey Seb! Apologies for the delay. Happy to help. Do you have a table that still has this error? The table shared above doesn't show this. Does it happen immediately after creating the column or when a table is duplicated?
The only fix I've found is adding a 'blank' header on this part with something simple like Content-Type: application/json so that I can still use my API keys in the normal headers
And check that table again on the "Create EmailBison Contact" column
I just ran a few of them to show
Hey Seb, Using your pre-saved header I was able to use it in the second column. Seems like everything is working now. Feel free to duplicate the changes to the main column: 1. Remove the auth field manually added in the header 2. Use the saved header (from the account) Let me know if you need anything else!
The issue is that on some tables I need to use different API keys for the same column dependent on different formulas that output different ones. If I have the same API key for each one, this would not work. What I think I have found is that if you do not have the 'account headers' set to anything, sometimes the column will not respond properly and think it is missing authentication, even if it is not. Does that make sense?
Ahh gotcha. Yes that make sense then yes it's a totally valid solution. Great job finding it!!!!
.png){kind=logo}
