FareHarbor · Tours and activities · Awaiting partner approval
FareHarbor bookings, waivers signed before check-in.
When someone books a tour in FareHarbor, the contact is sent your waiver with the activity and date filled in, so the check-in line is not a clipboard line.
Why connect FareHarbor
Three moments this is for.
The 8am departure
Twelve people on the sunset kayak are signed before they arrive. The guide checks a list, not a stack of paper.
The rebooked date
The storm moves Saturday's tour to Sunday. FareHarbor rebooks it; the old booking's unsigned waiver is voided and the new booking's is sent.
The activity that needs more
The zipline needs a height and weight declaration the paddle tour does not. Your requirements read the activity, so each booking gets its own.
How it works
FareHarbor sends the booking
FareHarbor posts every created, changed or cancelled booking to an address unique to your connection.
SignSealer re-reads it
FareHarbor cannot sign its webhooks, so — as FareHarbor itself advises — the address carries the secret and the booking is always read back from FareHarbor's API before use.
The contact is sent the waiver
Your requirements decide what the booking needs; the contact signs, and the packet shows it.
What comes across
What arrives from FareHarbor, and what SignSealer does with it.
| From FareHarbor | Used for |
|---|---|
| Booking UUID and display ID | The booking's label and your reference |
| Activity and start time | The facts your requirements read, and the date on the waiver |
| Contact name, email and phone | Who is sent the waiver |
| Customer count | How many people the booking is for |
| Status | Booked is worked; cancelled or rebooked voids what nobody signed |
Where it stands: awaiting partner approval
Built, and not connectable yet. FareHarbor grants API access to software partners case by case, after review and certification, and until it grants ours nobody can connect FareHarbor to SignSealer. We have applied; this page will say so the day it changes. FareHarbor's ‘SMS updates’ flag means a guest wants texts from FareHarbor about the booking, not from you through us, and is not read as consent. Links go by email. They go by text only to a guest whose consent to receive texts from you is on file in SignSealer: a booking system knowing a phone number is not that guest agreeing to be texted, and SignSealer never treats it as if it were.
Start today
What you can do now, without waiting.
Step 1
Today: use FareHarbor's booking notifications with Zapier or Make and SignSealer's Add or Update a Reservation action.
Step 2
Or send the waiver from your own booking confirmation using a SignSealer form link.
Step 3
When partner access is granted, connect in SignSealer under Integrations → FareHarbor.
Read the full FareHarbor guide How requirements decide what is sent
Questions
Why can I not connect it now?
Every call to FareHarbor's API carries a key FareHarbor issues to the software partner and a key per operator that the operator confirms. FareHarbor issues partner keys after reviewing and certifying the partner; until they issue ours, the integration has nothing to call with.
Does FareHarbor already have waivers?
FareHarbor has its own waiver feature. SignSealer is for operators who need the evidence behind a waiver — consent before signature, a sealed PDF, a certificate anyone can check — or who run more than one booking system and want one place for every signature.
Will each person in a group sign?
FareHarbor names the booking contact and counts the customers; it does not name each one. The contact is sent the waiver, and a group waiver or a per-person link from the packet covers the rest.
Will it text my guests?
Links go by email. They go by text only to a guest whose consent to receive texts from you is on file in SignSealer: a booking system knowing a phone number is not that guest agreeing to be texted, and SignSealer never treats it as if it were.
Ready when the next guest is.
Free for the first 25 agreements a month. No card to start.