- CategoryRentals
- AuthAPI key
Overview
Lodgify is a vacation-rental PMS. On /integrations, the Lodgify card opens the 'Connect Lodgify' modal. The modal asks for one field, 'API Key', labelled 'Paste your Lodgify Public API key'. If a Lodgify messaging channel is already connected on the same MessageMind account, the field is skipped and the server borrows that channel's key (keys: { source: "channel" }). A new Lodgify connection is subject to the one-PMS-per-account rule: disconnect another active PMS first. Reconnecting an already-live Lodgify connection remains allowed. Once connected, the AI can read your Lodgify properties, check availability, quote pricing, offer a prefilled booking link when a checkout slug is known, look up reservations, and respond to guest messages via webhooks subscribed to Lodgify's inbox events.
What MessageMind can do with it
- Import your Lodgify properties into the AI's catalog, resolved against a live property roster so a new property shows up without a manual re-import.
- Check availability for a property and date window, and quote pricing for a specific stay.
- Issue a prefilled booking link that lands on your Lodgify checkout page, when the checkout slug for your account is known.
- Look up a reservation and distinguish an enquiry from a booking, so an enquiry id is never read as a reservation id.
- Receive Lodgify webhooks for guest messages and the four booking events (new booking, new booked, booking change, booking status change).
- Pull back any host replies typed inside Lodgify's own inbox or in connected OTAs by reading the thread, since Lodgify publishes no webhook for host sends.
Requirements
- A Lodgify plan that includes Public API access.
- A Lodgify Public API key, or an already-connected Lodgify messaging channel on the same MessageMind account whose key the server can borrow.
How to connect
- In Lodgify, go to Settings, Public API and generate a Public API key. Treat it like a password and never share it.
- In MessageMind, open /integrations and click the Lodgify card. The 'Connect Lodgify' modal opens.
- Paste the key into the 'API Key' field (placeholder: 'Paste your Lodgify Public API key') and click Integrate. A 'Connecting Lodgify...' toast appears while the request is in flight.
- If a Lodgify messaging channel is already connected on the account, the API Key field is hidden and the server reuses that channel's key automatically (the client sends keys: { source: 'channel' }).
- On success the toast reads 'Lodgify connected.' (or 'Lodgify connected using your channel connection.' when the channel key was borrowed). On a bad key the toast reads 'Lodgify rejected that key. Check it is a Public API key and that your Lodgify plan includes Public API access.'
- Connecting imports nothing until you turn on Sync Properties in the Lodgify integration settings; it starts off.
Authentication and permissions
- Mechanism
- Static Lodgify Public API key sent on every call to the Lodgify API. No OAuth.
- Credentials
- One API key stored on your MessageMind tenant, or borrowed from the already-connected Lodgify messaging channel (social.lodgify) when the paste field is skipped.
Available data and actions
Reads
- Your Lodgify properties, resolved against a live TTL-cached roster.
- Availability and pricing for a requested stay.
- Reservations and enquiries referenced in a guest thread, with enquiries distinguished from bookings so an enquiry id is never read as a reservation id.
- Thread message history, including host replies typed inside Lodgify's own inbox or in connected OTAs (Lodgify publishes no webhook for host sends).
Writes
- Guest replies sent back into the Lodgify thread, each stamped with a minted idempotent message id so MessageMind can recognise its own sends when it re-reads the thread.
AI agent use cases
- Reply to Lodgify guest messages in-thread with property-specific answers.
- Hand a guest a prefilled booking link that lands on the right stay on your Lodgify checkout.
- Confirm reservation details for a returning guest without opening Lodgify.
- Pick up a reply you typed inside Lodgify's own inbox so the AI stays in sync with what the guest has already been told.
Configuration
- Sync Properties starts off after a connect. Turn it on in the Lodgify integration's settings to begin importing properties; nothing imports until then.
- Each connect subscribes one guest-message webhook plus the four booking webhooks (new booking, new booked, booking change, booking status change). Rate-change and availability-change events are not subscribed.
- Lodgify requires each subscription to have its own unique callback URL; MessageMind issues one URL per event per connected channel.
- The booking-link tool emits a link only when the checkout slug is known for your account. Without it, the tool declines to send a link rather than guess.
- A new Lodgify connection is subject to the one-PMS-per-account rule. Disconnect a different active PMS first; reconnecting an already-active Lodgify connection remains allowed.
Example workflows
Guest message to AI reply
- Lodgify delivers a guest_message_received webhook to the per-channel URL.
- MessageMind resolves the delivery to your tenant, normalizes the message and feeds it to the AI.
- The AI reply is posted back into the Lodgify thread with a minted idempotent message id so later reads of the same thread recognise it as our own send.
Connect by borrowing a channel key
- A Lodgify messaging channel is already connected on the account (social.lodgify is set).
- You open the 'Connect Lodgify' modal and the API Key field is not rendered.
- You click Integrate; the client sends keys: { source: 'channel' } and the server borrows the key that channel already holds.
- The success toast reads 'Lodgify connected using your channel connection.'
Limitations
- Lodgify publishes no webhook for messages the host sends; host replies are pulled back by reading the thread, not pushed.
- Rate-change and availability-change events are not subscribed; only guest messages and the four booking events are.
- Without a known checkout slug the AI cannot offer a working booking link and will say so instead of guessing.
- Public API access is a Lodgify-plan feature. Accounts without it cannot connect.
- The /integration/setup payload accepts exactly one Lodgify key; sending two is a 400.
Troubleshooting
The submit toast reads 'Paste your Lodgify Public API key.'
The API Key field was blank and no Lodgify channel is connected to borrow a key from. Paste a Public API key, or connect the Lodgify messaging channel first and reopen the modal.
The toast reads 'Add your Lodgify Public API key, there is no connected Lodgify channel to borrow one from.'
You tried to connect without a key while no channel is available. Generate a Public API key in Lodgify, Settings, Public API and paste it into the modal.
The toast reads 'Lodgify rejected that key. Check it is a Public API key and that your Lodgify plan includes Public API access.'
Verify the key was copied from Lodgify, Settings, Public API, and that the active Lodgify plan exposes the Public API. Older plans do not.
The toast reads 'Lodgify connection failed!'
A transient error or an unreachable Lodgify endpoint. Try again; if it persists, check Lodgify's status and your Public API plan entitlement.
No booking link is offered when a guest asks to book.
The checkout slug could not be resolved from your account. Reconnect, or reconfigure the account in Lodgify so the properties payload exposes it.
The AI does not know about a reply you just typed inside Lodgify.
Host replies are picked up on the next thread read, not by webhook. The next read of that thread will surface the message.
Disconnect and reconnect
- Open /integrations, open the Lodgify card and choose Disconnect. The stored API key reference is removed; if the server was borrowing the Lodgify channel's key, that channel is untouched.
- To reconnect, paste a fresh Public API key, or connect the Lodgify messaging channel first and reopen the modal to let the server borrow its key.
