@AliFarahat @gaurav @gnelson This is useful when integrating with external forms that use the POST method for redirecting a user after form submission.
Since you can’t just POST directly to any regular page in your app, you need to provide a url that can receive the POST data and return a response - ie, an API endpoint. The problem is that if this is happening as a result of a form submission, and the form redirects the user to the API response, the user will just see the JSON response on a blank page.
Not useful. So, the update gives us the option to change the response from JSON to a page redirect.
For example, when a Typeform or Google Form response is submitted… you usually have the option to redirect them to a web page like a Thank You or Confirmation… Those services make things easy and built in so that you can provide a regular web page url and you’re done.
However, there are other services where integration is a bit more manual and redirection happens via a POST call, especially when sending of data is necessary (validation, security, etc). So you need to redirect to an endpoint that can receive the data.
I’ve already seen two real Bubble world examples. The first was just an external form that needed somewhere to redirect users and it would only do it through a POST method.
The second was for a payment gateway integration. The payment form is hosted by the PCI compliant gateway, users fill out the form with their sensitive info, and when they click submit, the gateway POSTs to Bubble endpoint with whatever transaction data, and the user is taken to the redirected page for confirmation of form submission.
What’s cool is that Bubble lets you define two different pages based on a success or error response. Eg if the POST data didn’t contain a valid parameter to pass some kind of verification
Hope I didn’t botch the explanation and hopefully this makes sense!
And for those really interested, pretty sure what’s happening is this:
Gaby | Coaching Bubble
Private coaching, courses, and tons of free resources