The Hostaway integration verifies the guest of each new reservation in your Hostaway account automatically. You connect once, choose the workflow the verification runs and the verification timing, and every new reservation starts a verification for the guest when its verification opens (by default, as soon as it is created), without any manual step. The guest’s verification link is written straight onto the reservation as soon as it qualifies, and the verification’s status is mirrored there as it progresses, so your team sees it where they already work.
This page covers the Hostaway integration specifically. For the full list of available integrations and how connections work in general, see the Integrations overview.
When to use
Section titled “When to use”Connect Hostaway when you want reservations to trigger identity verification on their own, instead of adding each applicant by hand or through the API. It suits teams that:
- Take reservations in Hostaway and want every guest verified before arrival.
- Want the verification link and its live status visible on the reservation record, so reviewers and front-desk staff do not switch tools.
- Want to control which reservations get verified (for example, skip a particular channel, or run it on a different workflow) with routing rules rather than code.
If you only verify applicants occasionally, or you drive verification from your own system, the API or a bulk CSV import may fit better. You can use the integration alongside either.
How it works
Section titled “How it works”Once connected, the integration runs on its own:
- A reservation event arrives. Hostaway sends a webhook to a private, per-connection address whenever a reservation is created, modified, or canceled.
- A verification is created. The integration reads the reservation, applies your routing rules, and gives the reservation its verification link. When the reservation’s verification opens, it starts a verification bound to the default workflow you chose when connecting, or to the workflow a routing rule selects for it. The guest’s name, and their email and phone when present, are carried onto the applicant so reviewers can identify them in the console. The booking’s confirmation code is stored as the applicant’s external reference.
- The guest is invited, if the invite is on. A new connection, including one you connect again after a disconnect, starts with Send the verification invite off. Turn it on to have the platform email the guest their verification link; leave it off if you would rather send the link yourself from Hostaway using the link field described below. A connection that already exists keeps its setting, which the connection’s Edit drawer shows.
- The link and status are written back. Writing the verification link onto the reservation is queued as soon as the reservation qualifies, before any verification starts; writing an internal review link is queued when the verification is created. The fields appear once each delivery completes. The status field works the same way: an update is queued each time the verification moves through review to a final outcome.
A rule can have more than one condition, and it matches a reservation only when all of them match. For example, a rule can have two conditions: Location ID is one of L-100, and Source is not one of Example Channel. That rule matches each reservation at listing L-100 whose Source is not empty and is not Example Channel, in any capitalization. A reservation whose Source is empty does not match it. To include those reservations, use is not one of, or empty. The Integrations overview describes each operator.
A rule can also use Lead time (days), the number of whole days from the day a reservation was made to its arrival date:
- Lead time (days) is worked out from two dates, on the listing’s calendar. The integration reads the time a reservation was made as UTC, and places that time on the calendar of the listing’s time zone. So a reservation made at 9:30 PM listing time, on the evening before its arrival date, has a lead time of
1, not0.0is the same day. A reservation made after its arrival date has a negative lead time. The arrival date is used as Hostaway writes it and is not converted. The rule builder also offers is less than, is at most, is greater than, and is at least for this field. The Integrations overview describes them. - How a lead time is compared. As a whole number of days, so +03 matches 3.
- Lead time needs the listing’s time zone. Hostaway can send a reservation without its listing’s time zone. The integration then reads the time zone from the listing, and only when a rule needs the lead time. It does this for every reservation, whatever the arrival date. A listing gives no lead time if Hostaway cannot find it. It gives none if it has no time zone, or if the time zone is not a valid time zone name. A reservation also needs the time it was made and its arrival date.
- A reservation with no lead time matches no condition on it. Whatever the operator, no condition on Lead time (days) matches such a reservation. So a Skip verification rule on this field never skips it. A rule on another field, such as Source, still applies to it.
- A reservation whose dates are not set yet has no lead time. Hostaway can mark a reservation’s dates as not set yet. When Hostaway sends a reservation without that mark, the integration reads its arrival date as a real date, so a placeholder arrival date in the past gives a negative lead time.
Only the verification link, the review link, and the verification status are ever written back to Hostaway. No applicant personal data is sent to Hostaway.
Connecting Hostaway
Section titled “Connecting Hostaway”You need the Owner or Admin role, an active organization, and at least one workflow template to bind the connection to. Create a workflow first if you do not have one; the connect form links you to the workflow editor when none exist.
You connect using two credentials from your Hostaway account, an Account ID and an API key. Generate these in Hostaway under its API settings; both are required.
-
In the console, open Integrations and choose Hostaway.
-
Enter your Account ID and API key.
-
Choose the default workflow the integration runs for each reservation. This is required. Every verification the connection creates uses this workflow unless a routing rule skips the reservation or selects another workflow for it. The list shows your active workflows, with your organization default marked.
-
(Optional) Add routing rules. A rule can skip reservations that you do not want to verify, or run some reservations on a different workflow. Each rule has one or more conditions, and each condition compares a field (such as Source) with one or more values. When all of its conditions match, the rule either skips the reservation or selects the workflow it runs. A reservation that a Skip rule matches creates no verification. The connection also starts with a rule that skips inquiry and pending reservations. Checktiv adds that rule above the rules that you create here, so Checktiv evaluates it first. You can edit or remove it after you connect.
-
(Optional) Turn on the Send the verification invite toggle to have the platform email each guest their verification link. It is off for a new connection. Leave it off if you plan to send the link yourself from Hostaway using the written-back link field.
-
(Optional) Set the Verification timing. By default, verification opens when a reservation reaches Checktiv and is due at the first verification’s own deadline. To open it later or make it due at another time, see Verification timing.
-
Select Connect. The button stays disabled until a workflow is chosen and both credentials are filled.
On a successful connect, the platform registers the reservation webhook in your Hostaway account and creates the custom fields it writes back into (see below). The connection then appears in your Integrations list.
Fields we set in Hostaway
Section titled “Fields we set in Hostaway”The integration provisions three custom fields on your Hostaway reservations when you connect, and fills them automatically as verifications progress. All three are reservation-scoped text fields and are visible in Hostaway.
| Field name | When it is set | What it holds |
|---|---|---|
verificationStatus |
Queued when the reservation qualifies, then queued again with each update as it progresses | The verification’s current status for the reservation’s guest: Not yet open or Not started before a verification starts, then from in-progress through review to the final outcome, or Not completed by deadline. |
verificationLink |
Queued when the reservation qualifies | The reservation’s verification link for the guest. It stays the same for the whole verification window. Share this with the guest if you send invites yourself. |
verificationReviewLink |
Queued when the verification is created | An internal link your team uses to open the verification in the console. Not for the guest. |
A few details worth knowing:
- The verification link is queued when the reservation qualifies, and the review link when the verification is created; each appears on the reservation once its delivery completes. The verification link changes when the reservation is canceled (the link stops working), restored in Hostaway after a cancellation, or given a different guest name or email. See Verification timing. The status field works the same way: an update is queued as the verification progresses and appears once each delivery completes, so the reservation eventually reflects the current status, ending on the final outcome.
- A guest who opens the link again after finishing sees where their verification stands (for example, submitted and under review) instead of an error. The link never reopens a finished verification. A guest whose earlier verification lapsed before any paid check can start again from the same link while verification is open.
- Hostaway sends the check-in date without a time. A due time set in hours before check-in is therefore measured from the start of the check-in day in the listing’s time zone, or in UTC when the listing has none, so it can fall up to a day earlier than the guest’s arrival.
- These fields only ever carry the links and the status. They never carry the guest’s personal details.
- The written-back result lands on the exact reservation the verification came from, so a status cannot be recorded against the wrong booking.
Troubleshooting
Section titled “Troubleshooting”The connection shows “Reconnect needed.” The stored credentials are no longer valid, usually because they were rotated or revoked in Hostaway. Open the integration, choose to reconnect, and enter a fresh Account ID and API key. Your workflow, routing rules, and invite setting carry over.
A reservation did not create a verification. Check, in order:
- The verification timing. A reservation whose verification has not opened yet already has its link, and its status field shows Not yet open. Its verification starts when verification opens. See Verification timing.
- Routing rules. A reservation that matches a Skip rule is intentionally not verified, and one that matches a Select workflow rule runs that rule’s workflow instead of the default. Review the connection’s rules and the reservation’s fields (for example, its booking source).
- The reservation event. The integration acts on reservation events from Hostaway. A reservation created outside the connected account, or before the integration was connected, will not have triggered one.
- The workflow. The connection must be bound to an active workflow. A workflow an integration uses cannot be deactivated or deleted from the console or the API, but a connection set up before that protection can still point at an inactive default workflow. The connection’s form flags it; open the integration, choose Edit, and choose an active one. You can leave the credential fields blank.
A guest did not receive their invite.
Confirm the Send the verification invite toggle is on for the connection. A new connection starts with it off, and while it is off the platform does not email the guest; you are expected to send the link yourself using the verificationLink field written onto the reservation. Turning it on invites each guest whose verification opens after the change. To invite a guest whose verification already started, open it in your Applicants list and select Send invite (see Resend or revoke). If their verification has not started yet, share the link in the verificationLink field written onto the reservation. Also confirm the reservation carried a guest email, since there is no address to send to otherwise. If that email address reached the per-recipient invite limit of three invite emails in an hour, the verification starts but Checktiv sends no invite. Open that verification in your Applicants list and select Send invite.
The status is not showing on the reservation.
The status field (verificationStatus) is written when the reservation qualifies and updated as it progresses. If a reservation qualified but the field is empty, confirm the custom field still exists in Hostaway under its original name; reconnect the integration to recreate it if it was renamed or removed.