Loading...
Haven's native Guesty integration imports the listings you choose, keeps supported property and calendar data aligned, mirrors Guesty reservations in Haven, and sends confirmed Haven direct bookings and cancellations to Guesty.
For exact field directions, outbound behavior, polling windows, and the full webhook matrix, see Guesty Sync and Webhook Reference.
Native Guesty is generally available on every paid Haven plan — you connect it directly from your dashboard, with no waitlist or beta access required. If you'd rather connect through Airbnb than through Guesty, you can still connect supported Airbnb listings through Haven's direct Airbnb integration.
The Airbnb alternative connects Haven to Airbnb rather than to Guesty. It does not provide the native Guesty property, reservation, webhook, or calendar-write paths described below.
The token can be used once and expires after about four hours if unused. Generate it when you are ready to finish the connection.
Haven exchanges the one-time token for the credentials used by the ongoing connection. You do not need to create or paste a Guesty Open API client ID or secret.
During onboarding, you can choose:
After onboarding, use Your Guesty properties on the Integrations tab to select more listings. Select Auto-import properties to import future Guesty listings automatically, or Turn off to keep future imports manual.
If the import adds billable properties beyond your plan's included limit, Haven shows the applicable property-charge confirmation first.
Haven preserves Guesty's listing structure:
SINGLE listing becomes a standalone Haven property.MTL parent creates or reuses a Haven Multi-Unit Site. The parent is not imported as a separately bookable property.MTL_CHILD imports as its own Haven property inside that Multi-Unit Site.Haven uses the child nickname when available so similar units remain distinguishable. A calendar update for the Guesty parent refreshes its actively imported child units.
When Guesty supplies a supported value, Haven can import:
Haven-uploaded photos remain separate and are not removed or overwritten by Guesty photo sync.
Haven imports:
Guesty's listing-level default price, weekend price, and cleaning fee do not currently populate their matching Haven fields. Haven also does not import Guesty taxes, weekly or monthly price factors, full fee rules, or cancellation terms.
Security-deposit and extra-guest values can appear editable in Haven because they do not yet use the same field-lock registry as other synced fields. A later Guesty property refresh can replace them. Haven does not send those edits back to Guesty.
For each imported property, Haven reads:
Haven can send Haven-authored values for those same calendar fields to Guesty. It does not echo Guesty-sourced values back or blanket-write property-level base prices across Guesty's calendar.
To keep nightly pricing in Haven, enable Manage pricing in Haven from the property's Calendar → Pricing tab. Guesty daily prices then stop overwriting Haven prices. Those Haven-managed prices remain local rather than replacing Guesty prices, while eligible availability and stay-rule changes can still sync.
OTHER payment record.If a confirmed Haven booking cannot be created in Guesty after retries, Haven attempts to block the occupied dates in Guesty and notifies the account owner.
Haven's pricing engine and Stripe charge are authoritative for Haven direct bookings. Guesty's quote is an availability and booking-rule check; its amount does not replace the Haven total.
The OTHER payment record sent to Guesty is informational only. Guesty does not process the payment. Haven remains the system of record for:
Guesty labels every reservation with a source. Haven's direct bookings arrive with the source haven, which is how you tell them apart from Guesty booking engine, Airbnb, or Vrbo reservations in Guesty reports and automations.
Guesty creates a manual source the first time it actually receives a reservation using that name. Haven does not pre-register the source when you connect, so a newly connected account shows only the sources it already has, such as Guesty booking engine. Once your first Haven direct booking reaches Guesty, haven appears on its own in Guesty under Pricing & policies → Additional fees, in the Advanced capabilities (Manual Sources) group.
This is expected and is not a sign of a broken connection. If you have connected Guesty but have not taken a Haven booking yet, there is nothing to configure and nothing to fix.
Guesty's additional fees are read-only to Haven. Haven imports selected fee values but never creates fees in Guesty, never enables a fee's channel sync, and never changes which sources a fee applies to. That means:
haven source row starts with its sync toggle off and Include in Fare unchecked, the same as any other newly added manual source.haven source in Guesty, Guesty does not attach that fee to your Haven reservations.haven source affects Guesty's own records and reporting, not the amount Haven charged the guest.Guesty booking engine is Guesty's own direct-booking source and is present in every Guesty account whether or not Haven is connected. Seeing it active is a Guesty-side setting, unrelated to your Haven connection.
You may also see short-lived Haven names such as haven-policy-probe or haven-tax-probe in Guesty source lists. Haven uses those when it reads your tax and cancellation settings during sync. They never carry a real reservation, so you can leave them alone.
The native Guesty integration currently does not import, publish, send, or reply to:
Haven does not subscribe to Guesty message webhooks. It also does not push property content, photos, amenities, Wi-Fi, property-level fees, taxes, discounts, security-deposit settings, or cancellation rules to Guesty.
Haven-only areas remain editable and are not replaced by Guesty sync, including:
When Guesty supplies a registered property field:
Select a field's badge and choose Edit in Haven to create a local override. Guesty stops overwriting that field until you choose Re-sync from Guesty. Property-field overrides stay in Haven and are not pushed to Guesty.
Calendar and reservation sync use separate two-way rules. Enabling a local property-field override does not turn off Guesty calendar or reservation sync.
Haven subscribes to these Guesty webhooks:
| Guesty event | What happens in Haven |
|---|---|
reservation.new | Creates or updates a Guesty-managed unavailable event; Haven-originated echoes are suppressed |
reservation.updated | Updates or removes the mirrored event, or runs the supported Haven-originated cancellation behavior |
listing.new | Imports automatically only when Auto-import on is enabled; otherwise it remains available to select |
listing.updated | Re-fetches supported property content, amenities, house rules, photos, and mapped pricing fields |
listing.removed | Detaches the mapping, marks the Haven property removed upstream, removes active Guesty-sourced photos, and pauses add-on billing at renewal |
calendar.updated.v2 | Re-fetches the Guesty calendar; updates to an MTL parent refresh imported children |
guest.created | Validates and audits the event; Guest CRM updates when usable guest data arrives through reservation sync |
guest.updated | Validates and audits the event; it does not directly rewrite a Haven Guest CRM record |
Webhooks can take from a few seconds to about 30 minutes. Scheduled polling provides a safety net:
When Guesty sends listing.removed, Haven does not silently delete or archive the Haven property. Haven:
You can keep the Haven property, archive it from its property card, or import an available Guesty listing as appropriate. See Multi-Property Billing for billing details.
On Host Dashboard → Integrations, the Guesty card shows:
Guesty refreshes through imports, webhooks, and scheduled polling. There is no manual Sync button for Guesty. If a change has not arrived, check the connection and last-sync status, then allow the automatic webhook or safety poll to complete.
Disconnecting removes Guesty credentials from Haven, stops queued and future sync work, and archives the connection's mappings. Imported Haven properties and Haven-authored content remain.
To reconnect, generate a fresh one-time token from Guesty → Integrations → Marketplace → Book with Haven and use Connect Guesty in Haven. Previously imported properties remain in Haven; reconnecting does not restore an old token.
Native Guesty sync is available on any paid Haven plan. If you don't see the Guesty card, confirm you're on a paid plan and signed in to the workspace that owns the listings, then refresh the Integrations tab. You can also connect through the direct Airbnb integration if you prefer, or contact Haven support.
The token may have expired or already been used. Generate a fresh token from Guesty → Integrations → Marketplace → Book with Haven and try again.
MTL_CHILD.Guesty adds the haven manual source only after it receives its first Haven reservation, so the option is missing until you take a Haven direct booking on a mapped property. Confirm that the Guesty card shows Connection live and that the property was imported, then check again after your first Haven booking. See Haven as a Booking Source in Guesty.
Haven sends a booking only after Guesty's quote returns an applicable rate plan. If the push fails after retries, Haven attempts a protective Guesty calendar block and emails the account owner. Follow that notification and block the dates manually if Haven reports that the protective block also failed.
Guesty reported that the upstream listing was removed. The Haven property remains intact, but its Guesty mapping and sync have stopped and add-on billing pauses at renewal. Keep or archive the Haven property, or import an available Guesty listing as appropriate.
New to Haven?
Haven is the direct booking platform these guides are written for — a branded site, secure payments, and guest relationships you own. Build yours free.
Free to build · No credit card · Private until you publish
© 2026 Book With Haven, LLC.