Client Access to My App's Booking Form via Domain Masking

Questions
1

Hey everyone…

I am building an event management app. My app includes a booking form which my “Subscribers” need to allow their “Clients” access to.

I’m trying get my head around the possible ways to do this…

1) Embed the Booking Form
This is all possible, but is currently creating some problems on an Apple Mac and is not what all Subscribers want to do.

2) Link to the Booking Form
(e.g. myapp.com/booking-form/?s=123&e=456)
This is okay, but the booking form page the Clients land on is on my app’s URL rather than the Subscriber’s URL, and my test Subscribers aren’t liking that too much.

3) A Domain Masked Link to the Booking Form
So I’d ideally like my Subscribers to provide a link to my app’s booking form, but the url to appear to be coming from their domain. I understand this is called “Domain Masking”. In the ideal world, they would set up that
subscriber.com/booking-form
is actually taking their client to
myapp.com/booking-form
But their client’s browser still shows subscriber.com/booking-form.
They would then be able to pass in the parameters too, so a link to:
subscriber.com/booking-form/?s=123&e=456
is actually displaying:
myapp.com/booking-form/?s=123&e=456

Do any of you Bubblers out there know how to do this?

Many thanks! :slight_smile:
Antony.

2

Hi @antony,

Is exposing an API an option? That would give your subscribers full control over how they wish to “capture” the booking data on their own domain. Then, they’d simply post the data to your app’s endpoint. Of course, that’s potentially more work for them to set up, but it could also provide the most seamless experience for their clients.

Perhaps exposing an API as well as providing a simpler option, like one of the three you mention, might be worth considering?

3

Hi there @sudsy… thanks for the idea… but the booking-form page on my app has some immensely complex logic in it, so it definitely needs the actual page to be visited! :slight_smile: