Mindbody webhook - HEAD request

kenny · 2024-10-24T17:40:08.395Z

I am creating a webhook to capture Mindbody events. In Mindbody, first we create a subscription to the webhook where we include the endpoint url from bubble. In Bubble, a backend workflow is setup to detect data. upon trying to create the subscription, I get an error returned saying the endpoint URL is not responding. Mindbody technical support says:

“There seems to be an issue with this URL accepting HEAD and POST requests.
Currently, webhook URLs must accept HTTPS connections using TLS v1.2 or higher. Webhook URLs must accept both POST and HEAD HTTP requests. Mindbody uses POST requests to deliver events to the URL, and HEAD requests to check the URL’s validity when creating a subscription.”

Has anyone successfully setup a webhook with Mindbody/bubble? I have been successful with other webhook enablers (zapier, etc.) using Mindbody, but Bubble is putting up a roadblock it seems.

Jici · 2024-10-24T17:46:33.329Z

Did you remove /initialize after you detected data? Or you was not able to initialize it at all? Bubble doesn’t accept HEAD request in backend WF actually (I think it was the case before when you set it at GET, but it doesn’t work anymore)

kenny · 2024-10-24T18:34:43.160Z

Thanks Jici, I’m not able to detect data. Do you know what the reason for not accepting HEAD requests? any solution around this that you know?

Jici · 2024-10-24T18:41:46.804Z

From what i know there’s no solution inside Bubble. You may need to use third party tool and redirect request to Bubble as POST after.

You can create a request on ideaboard.

I just saw that I’ve answered you there for probably the same case

Is it possible to configure Bubble API endpoints to respond to HEAD requests (not POST requests)? APIs

@Jici thank you, but I don’t understand. I’m using POST to create a subscription for a webhook event. The provider says" Webhook URLs must accept both POST and HEAD HTTP requests. We use POST requests to deliver events to the URL, and HEAD requests to check the URL’s validity when creating a subscription.

And if at this moment HEAD was accepted in backend WF when set to GET, it doesn’t seem to work anymore

kenny · 2024-10-24T18:44:14.171Z

Thanks, very frustrating. I’ll make a request on the ideaboard