# Webhook Subscription Test 403

**URL:** <https://community.hubspot.com/t/webhook-subscription-test-403/11409>\
**Category:** APIs & Integrations\
**Created:** [November 26, 2018, 7:07pm UTC](https://community.hubspot.com/t/webhook-subscription-test-403/11409 "2018-11-26T19:07:57Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![runtheexe](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/runtheexe/32/29572_2.png) [@runtheexe](https://community.hubspot.com/u/runtheexe)\
**Post date:** [November 26, 2018, 7:07pm UTC](https://community.hubspot.com/t/webhook-subscription-test-403/11409/1 "2018-11-26T19:07:57Z")

</div>

Hello! I’ve set up a webhoook. When I test the subscription, I get a 403. The same request works when I use Postman. I’m not yet performing a security check against the X-HubSpot-Signature header, so the endpoint should be wide open.

I saw another topic ([Webhook test returning 500 Error](https://integrate.hubspot.com/t/webhook-test-returning-500-error/14004)) where it was suggested that HubSpot webhooks may have problems with wildcard certificates (which we are using)--is that a problem?

[

 ![](https://d2qpr2jzcazej7.cloudfront.net/original/3X/e/a/ea1928a3e92ad004cee191602fcd5e4086c93ac4.png)

image.png1920x968 61.1 KB

]([https://community.hubspot.com/legacyfs/online/uploads/default/original/2X/7/7e974e4cd64ac586eff29c65ff83adcd25a13150.png](https://community.hubspot.com/legacyfs/online/uploads/default/original/2X/7/7e974e4cd64ac586eff29c65ff83adcd25a13150.png))

---

<div class="post-metadata">

**Author:** ![IsaacTakushi](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/isaactakushi/32/70387_2.png) [@IsaacTakushi](https://community.hubspot.com/u/IsaacTakushi)\
**Post date:** [November 27, 2018, 9:38pm UTC](https://community.hubspot.com/t/webhook-subscription-test-403/11409/2 "2018-11-27T21:38:35Z")

</div>

Welcome, [@ac\_andrew](https://community.hubspot.com/u/ac_andrew)!

That may be the problem. Similar SSL-related errors with CRM Extensions were also recently discussed in [this topic](https://integrate.hubspot.com/t/ioerror-during-crm-extension-data-fetch/14270).

Can you confirm that [this](https://app.hubspot.com/developer/5177865/application/184468/webhooks) is your developer account and app? I’ll direct message you so that you can share the webhook URL you are testing.

---

<div class="post-metadata">

**Author:** ![runtheexe](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/runtheexe/32/29572_2.png) [@runtheexe](https://community.hubspot.com/u/runtheexe)\
**Post date:** [December 1, 2018, 2:49pm UTC](https://community.hubspot.com/t/webhook-subscription-test-403/11409/3 "2018-12-01T14:49:54Z")

</div>

Thanks so much [@Isaac\_Takushi](https://community.hubspot.com/u/isaac_takushi)

And thanks for link. Yes, that is my app.

Edit: I ran our domain through the utility at [SSL Server Test (Powered by Qualys SSL Labs)](https://www.ssllabs.com/ssltest/analyze.html) but did not see the errors discussed in the other thread.

---

<div class="post-metadata">

**Author:** ![IsaacTakushi](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/isaactakushi/32/70387_2.png) [@IsaacTakushi](https://community.hubspot.com/u/IsaacTakushi)\
**Post date:** [December 4, 2018, 4:07pm UTC](https://community.hubspot.com/t/webhook-subscription-test-403/11409/4 "2018-12-04T16:07:48Z")

</div>

Thanks for this information, [@ac\_andrew](https://community.hubspot.com/u/ac_andrew); I’ve shared it with the team.

We’ll investigate further! I appreciate your continued patience.

---

<div class="post-metadata">

**Author:** ![IsaacTakushi](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/isaactakushi/32/70387_2.png) [@IsaacTakushi](https://community.hubspot.com/u/IsaacTakushi)\
**Post date:** [December 6, 2018, 9:11pm UTC](https://community.hubspot.com/t/webhook-subscription-test-403/11409/5 "2018-12-06T21:11:20Z")

</div>

Hey, [@ac\_andrew](https://community.hubspot.com/u/ac_andrew).

One of our engineering team leads investigated your issue for a while this afternoon, but couldn’t identify the cause.

We’ve verified the request itself is correct and have tested it successfully locally, with cURL, and via Postman. It always returns a `204`, however when sent through HubSpot, the response is a `403`.

At this point, we unfortunately can’t answer the question as to why your service is rejecting HubSpot’s HTTP request and returning a `403`. Sorry we couldn’t be of more help in this matter.

---

<div class="post-metadata">

**Author:** ![runtheexe](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/runtheexe/32/29572_2.png) [@runtheexe](https://community.hubspot.com/u/runtheexe)\
**Post date:** [December 13, 2018, 9:54pm UTC](https://community.hubspot.com/t/webhook-subscription-test-403/11409/6 "2018-12-13T21:54:49Z")

</div>

Hello again, [@Isaac\_Takushi](https://community.hubspot.com/u/isaac_takushi)! Sorry for the delay in my response. Thanks so much for looking in to the issue.
