IntegrationsUpdated 11/9/2026

Lodgify Sync and Webhook Reference

This reference lists what Haven currently reads from Lodgify, what Haven writes to Lodgify, which Lodgify webhooks Haven uses, and the important limits of each path.

For connection instructions, see Connect Lodgify to Haven.

Direction Summary

Lodgify to Haven

Haven reads:

  • Property and room-type structure, listing content, and photos
  • Recognized amenities, house rules, and check-in/check-out times
  • Currency, default nightly rate, extra-guest pricing, and dated rate overrides
  • Fees (cleaning, linens, resort, management, pet, and mappable custom fees)
  • Taxes configured in Lodgify rate settings
  • Promotions that match Haven's discount types
  • Add-ons (imported as Haven upsells)
  • Minimum/maximum stay rules, advance notice, and booking window
  • Availability, closed periods, and preparation-time buffers
  • Bookings in every status, including tentative holds and blocks
  • Guest identity and contact data on bookings (into the Haven guest CRM)
  • Booking financials (totals, paid/due, quote line items)
  • Guest messages on booking threads
  • The cancellation policy and security deposit, via a quote probe
  • Each listing's rental agreement text, into your Rental agreements library (attached to no listing)

Haven to Lodgify

Haven writes:

  • Confirmed direct bookings (status Booked)
  • Booking requests (status Tentative) and inquiries (enquiries)
  • Confirmations and declines of pending bookings
  • Cancellations of Haven-originated bookings
  • Calendar blocks and unblocks for Haven-managed nights
  • Nightly rates and stay rules, when pricing is managed in Haven
  • A host-visible note on each pushed booking ("Booked on Haven")
  • Early check-in and late checkout times on the Lodgify booking, including the listing's usual times again after a refund. If Lodgify refuses the update, you still get a task to change the time by hand
  • Haven door codes (a smart-lock code or one you typed in Haven) as the key code on single-room Lodgify bookings
  • Guest portal messages onto the Lodgify booking thread

Not synced

  • Property content edits made in Haven are never written to Lodgify (Lodgify remains the source of truth for listing content)
  • Reviews — Lodgify's public API has no reviews endpoint, so Haven cannot import them
  • Lodgify per-person fixed taxes and fees with unmappable bases are reported, not approximated
  • Key codes on bookings that span several Lodgify rooms, and removing a key code when a booking is cancelled
  • External (channel-manager) bookings are recorded as metadata only

Identity and Structure

A Lodgify account is identified by its numeric user id (Lodgify has no "who am I" endpoint, so Haven reads it from the availability feed during connect). Each Haven listing maps to one Lodgify room type inside a Lodgify property — the sync key is propertyId:roomTypeId. A Lodgify property with several room types imports as several Haven listings that share address and house-level settings.

Room types with more than one unit currently import with calendar pushes restricted (Haven never writes blocks for a pooled room type); full multi-unit room support is rolling out separately.

Lodgify to Haven: Property Data

Core property fields

  • Title (property name; the room-type name is appended when a property has several room types)
  • Description (room description wins over the property description when both exist; HTML converted to plain text)
  • Max guests, bedrooms, bathrooms
  • Currency
  • Listed / unlisted status (is_active)
  • Photos, in the same order your Lodgify listing shows them, with captions

Address and location

Street address, zip, city, state, country, and coordinates import into the Haven location fields, and Haven composes the display address from those parts (Lodgify sends no pre-formatted one). Lodgify also sends no timezone, so Haven looks the listing's timezone up from the coordinates on the first import — check-in times, calendar days, and message timing then follow the property's real zone instead of a default. Lodgify's "hide address" preference is recorded but Haven's own address-privacy setting governs what guests see.

Lodgify's API does not share house rules text, arrival directions, guest access notes, the Wi-Fi network name or password, neighborhood or getting-around descriptions, or a property type. Those fields stay yours to write in Haven: the listing editor's sidebar card lists them under Worth checking (and the Visibility checklist under Lodgify doesn't share these) so you can fill them once, right in the card, or dismiss the ones that don't apply.

Amenities

Lodgify amenity entries are matched against Haven's amenity vocabulary in two passes: a direct name match first, then a text match through the shared amenity mapper. Amenities Haven can't recognize are recorded for review rather than dropped silently. Room-count entries (bedrooms/bathrooms) are handled as counts, not amenities.

House rules and times

  • Pets allowed
  • Adults only (imports as "not suitable for children")
  • Check-in and check-out hours (from Lodgify rate settings)

Cancellation policy and security deposit

Lodgify exposes your rental policy only inside booking quotes, so Haven prices two stays during import and refresh: the first bookable one and one about three months out. From those quotes:

  • Payment schedule — Lodgify's split (for example 50% at booking and the rest 7 days before arrival, or up to six payments such as 30% at booking, 30% 60 days out and the rest 30 days out) becomes Haven's payment schedule (Calendar → Price → Payment schedule), locked while Lodgify supplies it. A schedule Haven can't express exactly (more than six payments, a payment that isn't a whole percent) is left for you with a notice.
  • Cancellation policy — Lodgify's standard "All paid prepayments are non-refundable." becomes a non-refundable Haven policy. Together with the payment schedule that matches Lodgify exactly: a guest who cancels before the balance is due loses only what they already paid, and the balance is never charged. Other wording is read and converted into Haven refund rules.
  • Security deposit — imported when it is a fixed amount. Haven's deposit is one fixed amount per listing, so a percentage-of-reservation deposit is not imported; the deposit field shows a notice so you can set the amount. Lodgify does not report a deposit it doesn't collect itself (the Manually charge and refund deposit method), so that kind never reaches Haven — set it in Haven directly.

If a quote can't be priced (for example, no bookable date in the window), the fields it feeds are left unset — never guessed.

Rental agreement

When a Lodgify property has a rental agreement with text, the sync copies it into Settings → Trust & Safety → Rental agreements → Library as its own entry, named after the listing with (from Lodgify) at the end (for example Cocoa Tea Villa (from Lodgify)). Lodgify rental agreements appear in your Rental agreements library; attach one to a listing to use it. The import attaches it to no listing and turns nothing on, so checkout and the guest portal stay exactly as you set them until you pick it for a listing (Property settings → Manage agreement, or Attach to listings in the library editor) and require it.

Lodgify sends the agreement as formatted text; headings, bold, lists and links carry over. Lodgify has no fill-in blanks or merge fields, so review the wording and add any merge fields you want before you attach it.

When the text changes in Lodgify, the next sync updates the entry, and any listings you attached it to get the new version. Once you edit the entry in Haven, it is yours: later Lodgify changes no longer touch it. Archive or delete it and the sync does not bring it back. A Lodgify agreement that is only a link (Lodgify's agreement URL with no text) is not imported. Nothing is written back to Lodgify, and agreements you wrote in Haven are never changed.

Lodgify to Haven: Fees, Taxes, and Promotions

Fees

From Lodgify rate settings, fixed per-stay fees map onto Haven's named fee slots:

  • Cleaning fee, linens fee, resort fee, management fee
  • Pet fees (with their charge basis)

Other fees import as Haven custom fees when their basis maps exactly (fixed per stay, per night, per person, per person per night, or a percentage of the fare). Fees that only apply above a minimum number of nights, or with a basis Haven can't charge identically, are not imported — they're surfaced as sync notices so you can decide how to handle them, because importing them approximately would change what guests pay.

Haven's management fee and community fee can each be set to a flat amount or a percentage of the nightly rate, but a sync always writes a flat amount and resets the field to $. Unlock the fee field if you want to keep Haven's percentage. Your service fee ("keep the margin") is Haven-only and is never touched by a sync — see Your Service Fee (Keep the Margin).

Taxes

Taxes configured in Lodgify rate settings mirror into Haven tax rules:

  • Percentage taxes → percentage rules
  • Fixed per-stay taxes → flat per-booking rules
  • Account VAT is not mirrored — Lodgify does not say which amounts it applies to, so Haven never guesses

Per-person fixed taxes and account VAT are not imported (Haven has no per-person tax calculation; VAT's base is unverified). When a sync refuses a tax, the tax editor (Payouts → Tax rules → Manage) shows a notice naming each row and why, and Sync from Lodgify reports how many rows could not be mirrored, so you can add the tax as a Haven rule if it should apply to direct bookings. Mirrored rules are owned by the sync, and the editor's Sync from Lodgify button re-mirrors them on demand. To change one in Haven, click the Synced from Lodgify pill in the tax editor and choose Edit in Haven: Lodgify then stops updating this listing's taxes until you choose Re-sync from Lodgify, which replaces them with Lodgify's current taxes. See Taxes synced from your PMS. Your own Haven-authored tax rules coexist untouched.

Promotions

Lodgify promotions that exactly match a Haven discount type import into those fields: a percentage promotion with a 7-night minimum stay becomes the weekly discount, a 30-night minimum becomes the monthly discount, any other minimum stay becomes the trip-length discount, an "early booker" window becomes the early-bird discount, and a "last minute" window becomes the last-minute discount. Anything else — a fixed-amount promotion, one that needs a promo code, one limited to booking or stay dates, one combining several conditions, or a second promotion for a slot Haven only has one of — is reported as a notice on that pricing field rather than approximated, so you can decide whether to set it in Haven.

Add-ons

Lodgify add-ons with a fixed price import as Haven upsells (percentage add-ons are reported, not imported).

Lodgify to Haven: Calendar Pricing and Stay Rules

From the Lodgify rates calendar:

  • The default rate row becomes Haven's default nightly price, default minimum/maximum stay, and extra-guest pricing. Many Lodgify accounts send no default row; Haven then reads the extra-guest fee from the dated rates for the coming year when they all agree, and if the fee changes by season it leaves the field for you and shows a notice on it instead of picking one season
  • Dated rate rows become per-night price overrides and per-night minimum-stay overrides

From rate settings and availability:

  • Advance notice (days/hours) → Haven minimum advance days
  • Booking window → Haven maximum advance days
  • Preparation time between stays is recorded, and the buffer nights around bookings are kept unavailable in Haven (Haven has no turnover-gap field of its own; this is surfaced as a notice)
  • Check-in/check-out day-of-week restrictions from Lodgify import as Haven check-in/check-out day rules when they follow a weekly pattern

Per-night maximum-stay values and multiple rate tiers per day are not modeled in Haven; when Lodgify sends several rate tiers for one day, Haven uses the tier with the lowest minimum stay.

Lodgify to Haven: Reservations and Blocks

Booking statuses

  • Booked → confirmed reservation (holds dates)
  • Tentative → pending reservation (holds dates; the tentative expiry is recorded)
  • Open (an unconverted enquiry) → pending, holds no dates — matching Lodgify, which keeps those dates bookable
  • Declined, cancelled, or deleted → cancelled (dates released)
  • Unavailable → an owner block, not a guest reservation

Guest reservations

Each booking imports with dates, guest breakdown (adults/children/infants/pets), guest name/email/phone, source channel (Airbnb, Booking.com, Vrbo, Expedia, direct, iCal, email), booking timestamps, and financials (total, paid, due, and the quote's line items). Guests are added to your Haven guest CRM. Booking notes in Lodgify are not copied into Haven.

Blocks and closed periods

Lodgify closed periods mirror as blocked dates in Haven, labeled "Blocked via Lodgify." You can unblock one of these from Haven: open it on the calendar and click Unblock dates, and Haven reopens the same nights in Lodgify, so the block does not come back on the next sync. (Lodgify room types with several units are the exception: Haven cannot write availability for pooled units, so open those dates in Lodgify.) Preparation-time buffer days stay unavailable but are never treated as host blocks. Channel iCal blocks from Lodgify's calendar connections mirror as external blocks.

Haven to Lodgify: Direct Bookings

When a guest books on your Haven site:

  • Instant book → a Booked reservation is created in Lodgify immediately
  • Request to book → a Lodgify enquiry by default (no dates held); with Hold dates for requests on, a Tentative reservation holds the dates while you decide. Approving converts it to Booked; declining or expiry frees the dates. You can decide in Lodgify too: Accept there approves the request in Haven (the guest is charged as if you clicked Approve in Haven) and Decline there declines it
  • Inquiry → a Lodgify enquiry (no dates held)

Each pushed booking carries the stay total Haven charged (Lodgify displays it; Haven's Stripe charge remains the financial source of truth), the guest breakdown, and a booking note ("Booked on Haven") with the reservation details.

Guest email privacy

A booking request that does not hold dates is created in Lodgify as an Open booking: it leaves the dates bookable, shows the Haven total, and its conversation shows the guest's own message from the request as their message. Haven also attaches a note with the guest count, the guest's real contact details and the price breakdown. Accepting the request — in Haven or in Lodgify — flips it to Booked and approves it in Haven. Only when your Lodgify website has no active subscription — Lodgify then refuses every booking create — does the request arrive as a plain enquiry, and Lodgify's enquiry API has no price fields, so that enquiry shows no Due / Paid / Total and the note is where the amounts live.

In Lodgify, a Haven booking shows the Haven total as its total and amount due, with nothing marked paid (Haven collects the payment). Lodgify does not break that total into stay, fees and add-ons, so Haven writes the full breakdown into the booking's note: the stay, each fee, the add-ons the guest bought, any discounts, taxes and the total.

Pushed bookings carry a Haven alias email for the guest instead of their real address, so Lodgify's emails for the booking come to Haven instead of the guest. Replies you type in Lodgify's inbox appear in the Haven conversation and the guest portal within about 20 seconds on a conversation active in the last two hours (within two minutes on one active in the last three days), and Haven delivers them to the guest by email and text (the message itself plus a link to their guest portal). Lodgify sends Haven no notice of your replies, so Haven re-reads recently active conversations; older threads are re-read with the hourly sync. On a booking request, Lodgify can mark a reply you type in its inbox as Failed. That only means Lodgify's own email to the guest didn't go out; Haven still delivers the reply. Lodgify's automatic emails (booking received, request accepted and similar) are not forwarded, because Haven sends its own booking messages. Replies you type in Haven show in the Lodgify conversation, marked as already sent. The guest's real contact details stay in Haven.

Bookings Lodgify turns down

Lodgify checks every reservation against its stay rules for the arrival date: the minimum stay, and the days arrivals are allowed. It refuses a stay that breaks them, including one you add yourself in Haven, and it gives connected apps no way to book around them. A booking Haven sends onto dates Haven itself has blocked would otherwise land as an Open booking that holds no dates, so Haven lifts its own block for those nights right before it sends the reservation.

  • Before you book: on a listing synced to Lodgify, the manual booking dialog checks Lodgify's minimum stay for your arrival date and warns you when the stay is shorter. Lower the minimum in Lodgify first, and the reservation syncs in full.
  • If Lodgify refuses it: the booking stays confirmed in Haven. Haven blocks its dates on your Lodgify calendar so they can't be double-booked, emails you the reason, and shows Not in Lodgify yet on the reservation. Fix the rule in Lodgify (lower that date's minimum stay, or allow that arrival day), then click Retry on the reservation to send the full reservation with the guest and the price.
  • Don't add the reservation in Lodgify by hand. Haven would import it back as a second reservation.

If your Lodgify property takes its rates from an outside tool (Lodgify's external rates), Haven lowers that date's minimum stay for a booking you add yourself, creates the reservation, and puts the minimum back straight away.

Echo suppression

The mirror of a pushed booking coming back over webhooks/polling is recognized as Haven's own and never double-blocks dates or re-notifies you. Blocks Haven wrote to Lodgify are tagged so the return echo is attributed to Haven, not to Lodgify.

Haven to Lodgify: Calendar Writes

When Manage pricing in Haven is enabled for a listing, Haven pushes nightly rates and stay rules to Lodgify (in contiguous ranges, up to the standard 730-day horizon). Independent of pricing:

  • Blocking dates in Haven blocks them in Lodgify
  • Unblocking dates in Haven reopens them in Lodgify, whether Haven made the block or it came in from Lodgify as "Blocked via Lodgify". Dates a Lodgify reservation holds are never reopened from Haven.

Room types with multiple units never receive availability writes (rates still push — they're type-level).

Lodgify accepts rates only on a property that takes them from an outside tool (external rates). On a property priced with Lodgify's own rates, Haven's rates don't reach Lodgify; Haven still writes its blocks there.

Messaging

  • Guest messages on Lodgify booking threads arrive in Haven Messages (HTML converted to text, attachments as links)
  • Replies you type in Lodgify arrive in Haven Messages and the guest portal within about 20 seconds on a conversation active in the last two hours, within two minutes on one active in the last three days, otherwise with the hourly sync. A reply Lodgify marks Failed on a booking request is still delivered by Haven
  • Haven guest portal sends post onto the Lodgify booking thread as a real message
  • Operational mirrors ("Booking request received…") post as internal comments visible in Lodgify but never delivered to the guest

Live Availability Check During Haven Checkout

Before accepting payment, Haven re-checks the exact stay dates against Lodgify's live availability feed so a booking made moments earlier in Lodgify (or an OTA) can't be double-sold. Lodgify's API also enforces minimum-stay rules on booking creation, which Haven surfaces as a normal availability error.

How Ongoing Sync Happens

Initial import

Connecting imports every Lodgify room type automatically and keeps auto-import on for new ones; remove any you don't want from Your Lodgify properties (turn auto-import off to hand-pick instead). Each import brings content, photos, fees, taxes, rates, availability, and reservations, and runs the quote probe. A listing's rental agreement reaches your library on its first property refresh.

Property refresh

A property poll refreshes content, fees, taxes, settings and the rental agreement in your library roughly hourly, and detects room types deleted in Lodgify (their Haven listings are unlisted and flagged, never silently deleted).

Calendar and reservation polling

Calendar and reservations poll every few minutes as a webhook safety net, over the standard 730-day forward window. The reservation poll also sweeps Lodgify's reservation feed for closed periods webhooks may have missed.

Webhooks

Webhooks (below) deliver most changes within seconds; polling reconciles anything missed. A 15-minute health check re-subscribes any webhook Lodgify has dropped.

Lodgify Webhooks Haven Subscribes

Haven subscribes each connection to all ten Lodgify webhook events:

  • rate_change — refreshes the affected calendar
  • availability_change — refreshes the affected date range for every mapped room type of the property
  • booking_new_any_status, booking_new_status_booked — new bookings
  • booking_change — booking modifications
  • booking_status_change_booked, booking_status_change_tentative, booking_status_change_open, booking_status_change_declined — status transitions (a declined tentative releases its dates)
  • guest_message_received — new guest messages

Webhook Security and Delivery Behavior

Each subscription gets its own Haven endpoint URL with a random routing token, and its own signing secret issued by Lodgify. Every delivery must carry a valid HMAC-SHA256 signature (ms-signature header) or it is rejected. Duplicate deliveries are acknowledged without reprocessing. Transient failures on Haven's side return an error status so Lodgify redelivers (Lodgify retries up to 10 times); permanently unparseable payloads are acknowledged and surfaced to Haven engineering instead of being retried forever.

Disconnecting removes Haven's webhook subscriptions from your Lodgify account and deletes the stored API key.

Synced Fields and Locking in Haven

Fields that Lodgify owns (title, description, photos, fees, and so on) show a sync lock in the Haven listing editor; edit them in Lodgify and the change flows in. Calendar fields are two-way. Pricing direction flips when you enable Manage pricing in Haven: until then Lodgify's rates flow in; after, Haven's push out. Tax rules mirrored from Lodgify follow Lodgify, with an on-demand Sync from Lodgify refresh, until you choose Edit in Haven to manage them here.

Fields Haven never reads from Lodgify (for example, Haven-specific settings like your site design, markups, or guest-offer configuration) are always yours to edit.

New to Haven?

Everything in this guide, done for you

Haven is the direct booking platform these guides are written for — a branded site, secure payments, and guest relationships you own. Build yours free.

See how Haven works

Free to build · No credit card · Private until you publish