Wherewolf can request waivers to be signed for bookings made on your booking system. To make this possible Wherewolf can integrate with your booking system API and retrieve booking information.
Many booking systems work out of the box and only require some configuration and agreeing on which data will be shared between platforms. You can see these booking systems listed in the Dashboard https://dash.getwherewolf.com/integrations
If your booking system is not listed, you can still configure Wherewolf to fetch bookings using the Other Booking System Integration.
The Other Booking System Integration option provides a way to configure the different API endpoints that Wherewolf can then use to retrieve booking information. You will need to ask your booking system provider for this information.
To configure your Wherewolf App with a Other Booking System Integration, open the Wherewolf Dashboard, then open Integrations and find the Other Booking System Integration option.
Inside the Other Booking System Integration click the Connect button, you will be presented with a form to configure a header and a few API endpoints.
When filling in the details, you will have the chance to test each endpoint using "Test" buttons, use these to ensure Wherewolf is able to fetch data from your booking system.
Once you fill in the header and endpoint details you can click "Connect" to finish the process.
Headers
Headers allow to include extra details when one system is calling another one, Wherewolf will always include a header with every API call made to your booking system and is often used to authenticate the call and only answer valid ones.
Endpoints
Multiple endpoints are needed for a successful integration.
Health Check
The Health Check endpoint is used to confirm your booking system is reachable and more importantly to confirm that your Wherewolf app and your booking system are set to use the same Timezone
Get Activities
Your Wherewolf app will only ask for waivers to be signed when a booking is detected for an activity (aka product) that has been configured to require waivers. It is crucial to have the right list of activities configured in Wherewolf. To ensure the list of activities available in Wherewolf matches the list of activities available in your booking system, a "Get Activities" endpoint is needed.
Get Bookings
This is the endpoint Wherewolf will call to get a list of bookings for today or this week. Is meant to be the source of true and ensure Wherewolf is always aware of your bookings.
Get Booking
This endpoint is used to fetch the full details of a particular booking. Wherewolf may become aware of a new booking or a booking update via Webhooks that can be delayed on transit while the booking may be receiving extra updates. Wherewolf will always call your booking system to retrieve the latest details when a change is detected.
Update Guest Endpoint
Wherewolf can send waiver information back to your booking system, the goal is for your booking system to attach the waiver details to the original booking (order or ticket) in a way that helps you access these details easily. Wherewolf will send any new signed waiver (and any updates) when the waiver was signed under a known booking. Walk-in guests who sign waivers without a booking won't get their waivers sent to your booking system (the booking system won't have a place where to attach those).
Developers
If you are building an integration layer or endpoints to be used as an Other Booking System Integration, you can find the technical specification and requirements here: https://wherewolfnz.github.io/docs/integrations