Home
Events
Groups
Members

00 Clay Announcements
01 Community General
01 Props and Wins
01 Watercooler
01 Welcome and Intros
02 Bugs
02 Starting with Clay
02 Support
03 Feedback & Requests
03 Tutorials & Inspiration
04 FT Job Opps
Gtm Career Advice
Member Spotlight

Community Guidelines

Powered by Tightknit

Clay Not Saving Connection Credentials in HTTP Headers

·

·

Connection credentials in the form of HTTP Headers are not being saved by Clay: https://www.loom.com/share/1f07f4bd49004af4bc0917e1f284fac7?sid=8fba7a0c-f004-4e4c-ba24-ca298f9784e4

Clay Not Saving Connection Credentials in HTTP Headers | Clay

4 comments

· Sorted by Oldest

Channeled
APP
·
·
There could be a few reasons why your HTTP header credentials aren't being saved. First, ensure you're entering them correctly in the Headers (Optional) field when setting up your HTTP API request. If the issue persists, it might be related to your Clay API key. Check if it's properly configured by going to Settings > Your profile > API key. If you're still experiencing problems, could you please copy and paste the exact JSON you're using for the headers into the chat? This will help us troubleshoot further.
Sources: Workspace administration documentation | Documentation | Clay University HTTP API with Clay
João T.
·
·
No, I'd like to talk to a human
Bo (.
·
·
It is saving—it’s just that you won’t be able to view the headers directly in the UI after saving. Can you try running it to see if the connection works as expected? Let me know what happens!
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.