I’m intrigued by the new Webhooks feature. Can you give a quick explanation on how they’re different from the existing APIs?
3 Likes
I imagine first and foremost it’s simply great for better organisation - but they are baking in custom webhook services such as the Stripe webhooks, and no doubt others in the future, too.
This is a really great feature.
Hmm. But apart from separating them for tidiness, are they identical?
I haven’t made it work yet, but I believe (HOPE) that we can setup a single webhook in stripe, and then all the different event handlers will just be added in wappler by adding what we need to support. Plus it takes care of validating the webhook secret key. If I’m right, this is magnificent.
@George? I’m trying /webhooks/stripe as the webhook endpoint in Stripe and have added by secret key, but I’m getting an error on test:
{
"status": "500",
"message": "Webhook stripe has no handler."
}
Any brief instructions on setting up the webhook?
Thanks Ken. Yes, that’s what I’m thinking, too, but could do with a steer from the Wappler team on this. At the moment it doesn’t seem any different to any other API script.
Yes that is exactly how it is supposed to work.
Just add as webhook end point in stripe your server connect webhook folder as:
https://your_site_name/webhooks/stripe/
The last part is the webhooks name you entered. All the defined webhooks will be triggered from there. Right @patrick?
1 Like
Maybe try to add the last slash / after stripe in the webhook url.
Also make sure your website is published of course
We have to do a bit more work on the webhooks part, so more will be available next week 
We might even integrate with the Stripe CLI so you can test webhooks directly in Wappler
2 Likes
Ya, already tried the trailing slash...same.
The error is not a 404, so I am getting to the stripe webhook, it just can't get to the handlers.
Looking forward to next week!