APIs & Integrations

marcf
Member

HTTP 403 errors

Hi guys,

We have written an integration with HubSpot for our app which makes use of our mutual customer’s hapi keys from their profile. Late last week, we found that our requests are being blocked by the HubSpot servers and we are receiving an HTTP 403 error for the requests we’re making, which previously have been working perfectly. We changed our user agent string, and it started to work again immediately.

We contacted support, but they told us they cannot help with the API and to try and come here. Can you let us know why we would be getting this problem please? We have many mutual customers who lost a lot of data because of this and we don’t know what to tell them, as we can’t think of a reason that our user agent would be blocked.

Thanks,

21 Replies 21
ILamana
Member

HTTP 403 errors

Hi, It is also happening for me. I have updated the scopes but it is still happening. I haven't changed anything in my application, is there anything else I need to do?

0 Upvotes
CarltonBanks
Member

HTTP 403 errors

Any solution to this yet?

0 Upvotes
JCNunsys
Contributor | Elite Partner
Contributor | Elite Partner

HTTP 403 errors

The problem is in the Scopes, 😀

Apparently it is necessary to configure several scopes for it to work, I have made a short video 🤖

Juan Carlos Muñoz | NUNSYS​
Consultor Comercial – Especialista en CRM
686058665

Calle Gustave Eiffel, 3. Parque Tecnológico . Paterna , Valencia . 46980 . Spain
+34 960 500 631
www.nunsys.com
Facebook
Linkedin
Twitter
Youtube
JCNunsys
Contributor | Elite Partner
Contributor | Elite Partner

HTTP 403 errors

Hi, 

We connect Api HubSpot with Hubspot  Azure Data factory, and we having a trouble: ERROR [HY000] [Microsoft][Hubspot] (60) API Connection Failed (Unauthorized Access). Check credentials. HTTP Response code: 403 ERROR [HY000] [Microsoft][Hubspot] (60) API Connection Failed (Unauthorized Access). Check credentials. HTTP Response code: 403 Activity

MicrosoftTeams-image (18).png

Juan Carlos Muñoz | NUNSYS​
Consultor Comercial – Especialista en CRM
686058665

Calle Gustave Eiffel, 3. Parque Tecnológico . Paterna , Valencia . 46980 . Spain
+34 960 500 631
www.nunsys.com
Facebook
Linkedin
Twitter
Youtube
0 Upvotes
Sacha
Member

HTTP 403 errors

Hi,

I having a trouble "Client error: POST https://mydomain.zendesk....json resulted in a 403 Forbidden response: { “error”: { “title”: “Forbidden”, “message”: "You do not have access to this page. Please contact the account (truncated…) [details] { “error”: { “title”: “Forbidden”, “message”: “You do not have access to this page. Please contact the account owner of this help desk for further help.” } }

Can you help us,

Thanks a lot

0 Upvotes
psmith1
Member

HTTP 403 errors

Things are looking great for us - thanks for the quick response.

0 Upvotes
psmith1
Member

HTTP 403 errors

I am also seeing this as of 10:50 EST. Any details would be sincerely appreciated!

0 Upvotes
zwolfson
HubSpot Employee
HubSpot Employee

HTTP 403 errors

@psmith @cgalaiya This 403 response on the Contacts endpoint has been identified as a bug in our system. I will update the thread once we have more information. Thanks for reporting.

zwolfson
HubSpot Employee
HubSpot Employee

HTTP 403 errors

@psmith @cgalaiya this should be resolved now, let us know if you see anything else.

0 Upvotes
cgalaiya
Member

HTTP 403 errors

@dadams
Hi, I am also receiving a 403 error when trying to fetch a given contact. The endpoint was working a few days ago. Here is the relevant request id: 9f0fe0d4e2da8b70a49324fec2941dda. According to the error the access token does not have the contacts scope, but querying for the token’s information indicates the opposite.

0 Upvotes
mhp
Member

HTTP 403 errors

@dadams On November 4th this problem started occurring for me. I can confirm using httplib2 from Django fails with the 403, but the same endpoint contacts/v1/contact/createOrUpdate/email/:email work with cur.

0 Upvotes
Dadams
HubSpot Employee
HubSpot Employee

HTTP 403 errors

@mhp are you still getting those same errors at this point? In both of the previous cases in this thread the issue was temporary. If you’re still seeing this, are you logging the full response? There should be more details in the body of that error response.

0 Upvotes
mhp
Member

HTTP 403 errors

@dadams I am continuing to see the error. Response is a 403 with the content being a basic Access Denied page with “Reference #18.aef354b8.1482515978.1a2ba295” if that means anything to you.

0 Upvotes
Dadams
HubSpot Employee
HubSpot Employee

HTTP 403 errors

Thanks @mhp, I’ll need some other details so I’ll message you directly.

0 Upvotes
mattpamos
Member

HTTP 403 errors

PMed, Thank you for the help!

0 Upvotes
mattpamos
Member

HTTP 403 errors

@marcf, @dadams

I am having the exact same problem. My integration uses the blog-posts end point with a GET request. It has been working fine for 6 months, and now today I am getting 403 responses. Where you able to figure out your issue? (this same request works fine from another server, so I am suspect that my server got blocked somehow)

0 Upvotes
Dadams
HubSpot Employee
HubSpot Employee

HTTP 403 errors

@mattpamos can you message me directly with the same details for a request where you received a 403 error? This is likely a separate issue from the original post.

0 Upvotes
ankitATBodhi
Member

HTTP 403 errors

I am getting this error. Basically Hubspot plugin is not working on my O365 account. I am using Chrome.

 

DevTools failed to load SourceMap: Could not load content for https://oneshellprcorp.blob.core.windows.net/oneshellpr/20200710.2/plus.map: HTTP error: status code 403, net::ERR_HTTP_RESPONSE_CODE_FAILURE

0 Upvotes
marcf
Member

HTTP 403 errors

Thanks - sent you a message with that info!

0 Upvotes
Dadams
HubSpot Employee
HubSpot Employee

HTTP 403 errors

Hi @marcf

Did you happen to log the full response of those 403 responses? Can you message me directly with the details of a specific request or two that you saw those 403 errors for, including the full URL and the full response body if you have it? User agent isn’t something that we normally filter, so there may have been something else causing this.