HTTP API connection to Hubspot shows 201 in preview but 401 error in workbook

Alexis L. · 2026-01-26T21:35:22.224Z

Hi, I’m facing a very strange error, that’s I can’t much explain : my HTTP API connection to Hubspot is giving 201 in preview, and Error 401 in the workbook. Help ! 🙂

14 comments

· Sorted by Oldest

Clay Support
APP
·
·
A 401 in the table usually means the request is missing or not sending auth correctly, even if preview looks OK. Make sure your HubSpot header is exactly: Authorization: Bearer <your_token> (note the space after Bearer). [1]
In your table run, click into a cell showing “Missing authentication” to reveal the full error details (it often shows what header is missing).
Also, you can open Sculptor (top-right) and paste the error text + your intended HubSpot endpoint; it can help spot auth/header mismatches quickly.
If needed, verify the credential in Settings → Connections and use Test Connection for that account. [2]
Clay Support
APP
·
·
Is that what you were looking for?
Alexis L.
·
·
First there are no details there, and second I receive 201 in preview. Please enlighten me
Clay Support
APP
·
·
A 401 “Missing authentication” in the table run means the request being executed there isn’t sending valid auth, even if Preview shows 201.
Please double-check your HubSpot header is formatted exactly like this (including the space):
Authorization: Bearer <your_hubspot_token>
Also validate the credential you’re using in Clay:
1.
Go to Settings → Connections. [1]
2.
Find HubSpot (or the account tied to this HTTP API) and use … → Test Connection.
For faster diagnosis, open Sculptor (top-right), paste the error text and your HubSpot endpoint, and it can help spot auth/header mismatches. [2]
Clay Support
APP
·
·
Did that answer your question?
Clay Support
APP
·
·
If you still need help resolving the authentication issue with your HubSpot HTTP API connection, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any other errors you’re encountering?
Alexis L.
·
·
Hey - to a human, I found out after 1h the error: I had entered the Authorization header also in the HTTP parameters. For some reason, once you input those headers, they disappear and you can see them. Please tell the product team it would be great to fix that!
Clay Support
APP
·
·
Thank you for sharing your experience and feedback. I’m connecting you to a human teammate now who can assist further.
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)
Sayli G.
·
·
Hello Alexis, thanks for reaching out! Can you confirm if the issue was resolved? We hide headers after creating a connection to keep the API key safe and hidden in your workspace. This is why you can't see it once set up. If your HTTP API columns work correctly, it should not be a problem. I will share this feedback with the team.
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!
Alexis L.
·
·
Yes resolved
Alexis L.
·
·
Thank you
Andrew Q.
·
·
Going to close this one out but please reach out if anything comes up. Appreciate you!
🙌1

Clay Support
APP
·
·
A 401 in the table usually means the request is missing or not sending auth correctly, even if preview looks OK. Make sure your HubSpot header is exactly: Authorization: Bearer <your_token> (note the space after Bearer). [1]
In your table run, click into a cell showing “Missing authentication” to reveal the full error details (it often shows what header is missing).
Also, you can open Sculptor (top-right) and paste the error text + your intended HubSpot endpoint; it can help spot auth/header mismatches quickly.
If needed, verify the credential in Settings → Connections and use Test Connection for that account. [2]
Clay Support
APP
·
·
Is that what you were looking for?
Alexis L.
·
·
First there are no details there, and second I receive 201 in preview. Please enlighten me
Clay Support
APP
·
·
A 401 “Missing authentication” in the table run means the request being executed there isn’t sending valid auth, even if Preview shows 201.
Please double-check your HubSpot header is formatted exactly like this (including the space):
Authorization: Bearer <your_hubspot_token>
Also validate the credential you’re using in Clay:
1.
Go to Settings → Connections. [1]
2.
Find HubSpot (or the account tied to this HTTP API) and use … → Test Connection.
For faster diagnosis, open Sculptor (top-right), paste the error text and your HubSpot endpoint, and it can help spot auth/header mismatches. [2]
Clay Support
APP
·
·
Did that answer your question?
Clay Support
APP
·
·
If you still need help resolving the authentication issue with your HubSpot HTTP API connection, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any other errors you’re encountering?
Alexis L.
·
·
Hey - to a human, I found out after 1h the error: I had entered the Authorization header also in the HTTP parameters. For some reason, once you input those headers, they disappear and you can see them. Please tell the product team it would be great to fix that!
Clay Support
APP
·
·
Thank you for sharing your experience and feedback. I’m connecting you to a human teammate now who can assist further.
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)
Sayli G.
·
·
Hello Alexis, thanks for reaching out! Can you confirm if the issue was resolved? We hide headers after creating a connection to keep the API key safe and hidden in your workspace. This is why you can't see it once set up. If your HTTP API columns work correctly, it should not be a problem. I will share this feedback with the team.
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!
Alexis L.
·
·
Yes resolved
Alexis L.
·
·
Thank you
Andrew Q.
·
·
Going to close this one out but please reach out if anything comes up. Appreciate you!
🙌1