Jul 22, 20227:39 AM - edited Jul 22, 20227:47 AM
Participant
Webhook API creating a subscription
SOLVE
Hi,
We want to make use of the Webhook API of HubSpt. So we make use of the HubSpot PHP API client. I wrote a service class in our Laravel project to interact with the client.
We make use of OAuth 2.0 implementation. Any endpoint works as expected, except for "/webhook" endpoints. Below is the problem.
HTTP 401 Unauthorized - body: { "status":"error", "message":"Authentication credentials not found. This API supports both API Key and OAuth 2.0 authentication and you can find more details at https://developers.hubspot.com/docs/methods/auth/oauth-overview", "correlationId":"8cf5ae15-0824-4941-b533-5c30d5c5aaa4", "category":"INVALID_AUTHENTICATION" }
Has anyone run into the same problem and how did you solve it? Or am I doing something wrong?
Jul 22, 20229:53 AM - edited Jul 22, 20229:54 AM
Participant
Webhook API creating a subscription
SOLVE
I've read the documentation again and some other threats, and now it works. I solved the problem by generating a "HubSpot Developer Key". This must be used as "API Key".
Now I getting the following response:
HTTP 400 Bad Request - body: { ... "message": "Failed to handle unknown subscription type `ticket.propertyChange`. Please contact support." }
How should we proceed in this case? I tried authenticating with both OAuth and Private Apps access tokens but the only response I receive back is 401 Unauthorized
Our Webhooks APIs all work to create the config via a Developer App, not a standard HubSpot Account where the Hapikey is used.
As such, requests must be authenticated using a Developer API Key which is separate to the Hapikey functionality that we have deprecated. Please see here for more information:
Jul 22, 20229:53 AM - edited Jul 22, 20229:54 AM
Participant
Webhook API creating a subscription
SOLVE
I've read the documentation again and some other threats, and now it works. I solved the problem by generating a "HubSpot Developer Key". This must be used as "API Key".
Now I getting the following response:
HTTP 400 Bad Request - body: { ... "message": "Failed to handle unknown subscription type `ticket.propertyChange`. Please contact support." }
You're getting this response as the 'ticket.propertyChange' isn't quite ready for release yet. This is a work in progress and our docs were a step ahead, apologies for the confusion.
We're updating the docs and will roll this out as soon as it's ready.