# Unauthorized **URL:** \ **Category:** APIs & Integrations\ **Tags:** developer-tools\ **Created:** [November 21, 2019, 9:51pm UTC](https://community.hubspot.com/t/unauthorized/17347 "2019-11-21T21:51:25Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![Derek\_Gervais](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/derek_gervais/32/17429_2.png) [@Derek\_Gervais](https://community.hubspot.com/u/Derek_Gervais)\ **Post date:** [December 3, 2019, 3:18pm UTC](https://community.hubspot.com/t/unauthorized/17347/4 "2019-12-03T15:18:23Z")
Hi @dianacch , Apologies for the delay here. As far as I understand, it’s not required that your client has an SSL certificate in order to make requests to the HubSpot API. This appears to be validated in this [stack overflow article](https://security.stackexchange.com/questions/110621/ssl-newbie-does-https-client-also-need-a-certificate). That said, I’m not really clear on what exactly is happening here. A 401 with a hapikey almost always means one of two things: 1. The request is being malformed in some way, so that the hapikey isn’t being properly included 2. The hapikey is a developer hapikey (from a developer account) and is used to make requests to a test or production portal Can you potentially log the raw request body you’re sending to the HubSpot API (minus the actual hapikey) so that we can take a closer look? Additionally, can you confirm the Hub ID of the account you’re using? --- _[View the full topic](https://community.hubspot.com/t/unauthorized/17347)._