Hostaway · Vacation rentals · Beta
Hostaway bookings in, signed agreements out.
Each new Hostaway reservation sends the guest the agreement and waivers that listing needs, re-read from Hostaway so what they sign matches the booking.
Why connect Hostaway
Three moments this is for.
Forty listings, forty sets of rules
The cabin with the dock needs a water waiver; the city flat does not. Your requirements read the listing, the guest count and the channel, so each booking gets its own packet.
The guest who books through Vrbo
The channel does not change the paperwork you need. Every reservation Hostaway takes, from any channel, arrives the same way.
The group that grew
The reservation is modified from four guests to six. SignSealer re-reads it, keeps what was already sent to the lead guest, and your per-adult rules add what the new count needs.
How it works
Connect with an API key
Create a Hostaway Public API key in your own dashboard and paste it with your account ID. SignSealer registers its webhook with Hostaway for you.
Hostaway tells us
Hostaway's webhooks are not signed, so SignSealer registers a login of its own and refuses any delivery without it — then re-reads the reservation from Hostaway's API.
Your rules decide
The reservation meets your requirements and the guest is sent what they owe. The packet shows what is signed and what is not.
What comes across
What arrives from Hostaway, and what SignSealer does with it.
| From Hostaway | Used for |
|---|---|
| Reservation ID and listing | The reservation's label, and the property your rules read |
| Arrival and departure dates | When the stay starts, and which age counts as a minor |
| Guest name, email and phone | Who is sent the agreement |
| Adults, children, pets and total guests | Facts for rules like a pet addendum or a per-adult waiver |
| Channel | Airbnb, Vrbo, Booking.com or direct, for rules that differ by channel |
| Status | New and modified stays are worked; a cancellation voids what nobody signed |
Where it stands: beta
Built against Hostaway's published Public API and tested against it on our side, not yet with a live Hostaway account. It needs no partnership: the key is one you create. Listing on the Hostaway Marketplace is a separate certification we have not started. 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.
Getting started
About five minutes.
Step 1
In Hostaway: Settings → Hostaway API → Create, choosing Hostaway Public API. Copy your account ID and the key.
Step 2
In SignSealer: Integrations → Hostaway → Connect, and paste both.
Step 3
Decide whether bookings send straight away, and check your requirements for each kind of listing.
Read the full Hostaway guide How requirements decide what is sent
Questions
Is the webhook secure if Hostaway does not sign it?
Each delivery must carry a login and password SignSealer made for your connection, at an address unique to it — and even then SignSealer uses the delivery only to learn which reservation changed, then reads that reservation from Hostaway itself. A forged delivery cannot put anything into your account.
Does it write anything back to Hostaway?
Not in this version. SignSealer reads reservations; your team sees who has signed on SignSealer's side. Writing a note or custom field back to the reservation is the next step.
What about Hostaway's own guest messaging?
It is untouched. SignSealer sends its own signing email; your Hostaway messages carry on as before.
Can the link go by text?
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.