It has come to our attention that OnceThere product has been discontinued. As a result, the integration is no longer supported. Please reach out to our Technical Support team with any questions or concerns.
OnceThere enables hotels and lodging providers to complete their guest experience by curating and selling tours/activities to visitors more efficiently, both on their website and in situ.
Destination Marketing Organizations (DMOs) and Visitors Bureaus use OnceThere to easily book tours and activities for visitors in their cities, both through their website and on-location kiosks. The OnceConnect solution saves DMOs valuable time by not needing to call activity providers, thus improving traveler experience and turnaround in their city.
Get more exposure for your inventory of tours and activities by distributing them through OnceThere partners in cities around North America.
Features of OnceThereBack to top
- OnceThere operates similar to Expedia, but instead of listing only on Expedia, your items will be listed on other company's websites too, such as the Local City Tourism site.
- End-users can create multiple reservations across different Checkfront accounts in a single booking though OnceThere.
How Does it Work?Back to top
- Information from Checkfront is called via API in real-time as an end-user loads a page with OnceThere in it.
- When a booking takes place, the end-user selects their tour/activity on one of OnceThere's distribution partners (a tourism office website for example). They proceed through OnceThere's Payment Provider (Stripe) and complete their booking.
- The booking details are sent to Checkfront via the API and your records/inventory are updated.
Checkfront Tip: What is an API?
API is the acronym for Application Programming Interface, which is a software intermediary enabling two applications to talk to each other. Each time you use an app like Facebook, send an instant message or check the weather on your phone, you’re using an API.
Imagine this; you’re sitting at a table in a restaurant with a menu of food to order from. The kitchen is the part of the system that will prepare your order. What's needed though, is the critical link to communicate your order to the kitchen and then deliver that order back to your table. This is where the waiter (API) comes in. The waiter is the messenger (API) that takes your order (request) and tells the kitchen (the system) what to do. The waiter then delivers the response back to you. In this case, it is the food you ordered.