The Hostaway integration starts an identity verification automatically whenever a reservation is created in your Hostaway account. You connect once, choose the workflow the verification runs, and every new reservation mints a verification for the guest without any manual step. The guest’s verification link is written straight onto the reservation, 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) 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 starts a verification bound to the workflow you chose when connecting. 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. By default, the platform emails the guest their verification link. You can turn this off if you would rather send the link yourself from Hostaway using the link field described below.
- The link and status are written back. Writing the verification link and an internal review link onto the reservation is queued when the verification is created, and the fields appear once that delivery completes. The status field works the same way: an update is queued each time the verification moves through review to a final outcome.
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 sends the reservation elsewhere. The list shows your active workflows, with your organization default marked.
-
(Optional) Add routing rules to skip reservations you do not want to verify. Each rule matches a field (such as the booking source) against one or more values. A reservation that matches a skip rule creates no verification. Leave this empty to verify every reservation.
-
(Optional) Set the guest invite toggle. It is on by default, so the platform emails each guest their verification link. Turn it off only if you plan to send the link yourself from Hostaway using the written-back link field.
-
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 verification is created, then queued again with each update as it progresses | The verification’s current status for the reservation’s guest, moving from in-progress through review to the final outcome. |
verificationLink |
Queued when the verification is created | The guest’s durable verification link. 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 link fields are queued when the verification is created and appear on the reservation once that delivery completes. 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.
- 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:
- Routing rules. A reservation that matches a skip rule is intentionally not verified. 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. If the bound workflow was deactivated, reconnect and choose an active one.
A guest did not receive their invite.
Confirm the guest invite toggle is on for the connection. If you turned it off, the platform does not email the guest; you are expected to send the link yourself using the verificationLink field written onto the reservation. Also confirm the reservation carried a guest email, since there is no address to send to otherwise.
The status is not showing on the reservation.
The status field (verificationStatus) is written when the verification is created and updated as it progresses. If a reservation started a verification 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.