How to stop receiving webhooks after a customer churns in HubSpot?
Hello,
We have a question regarding webhook integration with HubSpot. When a customer churns from our side and is removed from our system, we would like to know if there is an endpoint in HubSpot that allows us to uninstall the application only for that particular customer.
Currently, we receive a large number of webhooks from HubSpot every day for customers who have churned, and this is affecting our infrastructure, finances, and environmental impact.
To stop receiving webhooks for a particular customer who has churned, you can use the HubSpot's "unsubscribe" endpoint. This endpoint allows you to unsubscribe the customer's email address or a specific event subscription from receiving webhooks.
Here are the steps you can follow:
Identify the customer who has churned and whose webhooks you want to unsubscribe. Use the "unsubscribe" endpoint to unsubscribe the customer's email address or a specific event subscription. The "unsubscribe" endpoint requires the email address or event subscription ID that you want to unsubscribe.
Here is an example of how you can unsubscribe a customer's email address:
Replace :appId with your HubSpot application ID, :subscriptionId with the subscription ID that you want to unsubscribe, and :email with the email address of the customer you want to unsubscribe.
Alternatively, if you don't have the subscription ID, you can also use the customer's email address to unsubscribe from all events:
As noted by @boubacardabo, we have attempted to utilize the various endpoints you have provided. However, we consistently receive 404 errors in the API responses, and the hooks continue to proliferate.
We aim to establish a "churn" flow on our side, incorporate this request into it, and streamline the reception of hooks to cleanse our application. Currently, we are facing a substantial number of "404" errors returned to HubSpot due to this issue.
We have implemented a solution using the endpoint you provided and it looks like the URL is unreachable. We also looked for clues in the official documentation with no success for a dedicated endpoint for unsubscribing.
Can you please help us with further details or another working endpoint ?