# Lodgify

A booked stay in Lodgify sends the guest the agreement and waivers that property needs, read back from Lodgify so what they sign matches the booking.

> **Beta.** Built against Lodgify's published API and webhook documentation and tested against stand-ins on our side, not yet run against a live Lodgify account, which is why it is beta. It needs no partnership: the key is one you copy from your own account. That key reads and writes all of Lodgify; SignSealer uses it only to read properties and bookings and to manage its own webhooks. Links go by email. They go by text only to a guest whose consent to receive texts from you is on file in SignSealer: a booking system knowing a phone number is not that guest agreeing to be texted, and SignSealer never treats it as if it were. Texts go from your business's own number, which is coming soon.

## Before you start

- The membership: connecting a booking system comes with it ([how that works](https://signsealer.com/docs/integrations)). On Free, your 10 signings a month are sent from the dashboard.
- A SignSealer account with the terms signed and a published form for each document.
- Access to your Lodgify account's settings, to copy its API key.
- Once it is connected, documents chosen on its page for what each property's bookings need.

## Connect Lodgify

1. In Lodgify, open **Settings → Public API** and copy the **API key** shown there. It opens your whole Lodgify account, so treat it like a password.
2. In SignSealer, open [Integrations](https://app.signsealer.com/integrations), choose **Lodgify → Connect**, and paste the key.
3. Choose the settings and press **Connect Lodgify**. SignSealer reads your properties with the key (proving it), then subscribes its webhooks in Lodgify for you.
4. Make a test booking in Lodgify, mark it Booked, and watch it arrive under the connection's activity.

## What SignSealer sets up in Lodgify

Four webhook subscriptions (`POST /webhooks/v1/subscribe`), one each for `booking_new_status_booked`, `booking_status_change_booked`, `booking_change` and `booking_status_change_declined`. Lodgify wants a different address for each subscription, so each is this connection's delivery address with `?event=` and the event's name after it. Lodgify gives each subscription its own signing secret, once, and SignSealer seals all four. Enquiries are not subscribed to. If one subscription is refused while connecting, the ones already made are removed again. Disconnecting unsubscribes all four; a new address subscribes them again.

## What comes across

| Lodgify | In SignSealer | Notes |
| --- | --- | --- |
| **id** | Reservation external ID | Keys the reservation, so every update is the same reservation |
| **property_id, and the property's name** | Label, and facts: property, property_name | “Fjord House · #880011”; the name is read from the property when the booking does not carry it |
| **arrival / departure** | Starts on / ends on |  |
| **guest name, email, phone** | Primary guest | Recognized on update by the Lodgify guest ID |
| **guest breakdown: adults, children, infants, pets; each room's people** | Facts: guests, adults, minors, pets | Children and infants are both minors; a booking of several rooms is added up |
| **source** | Fact: channel | Where it was booked, as Lodgify names it (AirbnbIntegration …) |
| **status** | What happens | Booked: worked · Open (an enquiry), Tentative: ignored · Declined: canceled |

## Documents that read it

The reservation carries these facts, which a document's *Only bookings where* can read: `guests`, `adults`, `minors`, `pets`, `channel`, `property` and `property_name`. For example, a waiver for every adult on stays with more than six guests is *Each adult*, *Only bookings where* guests *is more than* 6.

Documents are chosen under **Documents for bookings** on the connection's page in [Integrations](https://app.signsealer.com/integrations) (there is no API route for them yet); see [Reservations and packets](https://signsealer.com/docs/packets).

## How a delivery is proven

Lodgify signs each delivery with an `ms-signature` header: `sha256=` and the HMAC-SHA256 of the exact body under that subscription's secret, in upper-case hex. SignSealer checks it in constant time against each of the connection's secrets, and only then reads the body. It carries no timestamp and Lodgify gives a delivery no id, so the event is the booking and the exact bytes: a redelivery is a duplicate, and a replay can at most make SignSealer re-read one of your own bookings, because the booking is always read back from Lodgify's API (`GET /v2/reservations/bookings/{id}`) before anything is built from it. Signed events that are not about a booking are accepted and ignored.

## Settings

| Setting | Choices | What it does |
| --- | --- | --- |
| **When a booking arrives** | Send straight away (default) · Build the list and wait | Straight away starts everything the packet owes as soon as the booking is worked. Waiting builds the reservation and its packet and sends nothing until somebody presses Send on the reservation, or your code calls `POST /v1/packets/{id}/start`. |
| **When a booking is canceled** | Void what nobody has signed (default) · Leave it | Voiding marks every unfinished document with the reason and the packet void. Anything already signed is kept: an executed waiver is evidence of what was agreed. |

What each guest is sent is decided by the connection's **documents for bookings**, chosen on its page: each says which document, who signs it — the person who booked, every adult, or a parent or guardian for each minor — and which bookings, read from the reservation's facts (dates, guest counts, property, channel). A default covers the bookings nothing else fits, and a booking that matched nothing says so in the connection's activity ([Reservations and packets](https://signsealer.com/docs/packets)).

## Texting and consent

Signing links go by email. They also go by text only when SignSealer holds that guest's consent to receive texts from your business, recorded with the exact words they agreed to — at your counter, on your booking form through `POST /v1/sms-consents`, or on SignSealer's own opt-in. That check runs when the link is queued (`app.may_text`), not in the integration.

No booking system can give SignSealer that consent, so none is treated as if it could. Each adapter records what the provider's data said — `VERIFIED_CONSENT`, `NO_CONSENT` or `INSUFFICIENT_EVIDENCE` — and only `NO_CONSENT` changes anything: the guest's number is not written at all. Every provider built so far can only ever say `INSUFFICIENT_EVIDENCE`. The connection's activity shows, for each guest with a number, whether the link was also texted and why not.

[How to record consent you took yourself](https://signsealer.com/docs/texting).

## Duplicates, order and retries

- **Once.** A delivery is recorded once per connection and event id. A provider that redelivers the same event gets `200 {"duplicate": true}` and nothing happens twice.
- **Newest wins.** Each event means "read this booking as it is now". A newer event about a booking supersedes an older one still waiting, and one booking is never worked twice at once.
- **Nothing is sent twice.** Guests are recognized by their id in the provider (or by address and name), so an update keeps each guest's link to what they were already sent.
- **Retries.** A failure is retried after 1, 2, 4, 8 … minutes, up to six hours apart, and gives up after eight tries. It is then listed, with its reason, under the connection's activity, where it can be tried again once whatever refused it is fixed.
- **The reason is in our words.** What the activity says of a failure is one plain sentence about what happened and what to do: the provider refused our credentials, did not answer, is limiting us, answered with an error, or says the booking or listing does not exist. It carries the provider's status code where there is one, such as `(422)`, and a short reference to quote if you write to us. What the provider itself wrote back is not kept or shown, because it can quote a guest's name, email or phone.
- **Refused credentials.** If the provider refuses SignSealer's credentials, the connection goes to *needs attention* and stops working events until new credentials are given. What arrives meanwhile is kept and worked afterwards.
- **Retention.** What arrived is cleared thirty days after it was worked; the outcome and the reservation it made are kept.

## Troubleshooting

| What you see | Why | What to do |
| --- | --- | --- |
| **“Lodgify refused our credentials” when connecting** | The key is wrong, or was replaced in Lodgify | Copy the key again from Settings → Public API and paste it |
| **Needs attention after it worked** | Lodgify stopped accepting the key | Paste the current key on the connection's page; waiting bookings are then worked |
| **An enquiry or a tentative booking never arrives as a reservation** | Only booked stays are bookings | It is worked when Lodgify marks it Booked |
| **Deliveries refused (401)** | The subscriptions were changed outside SignSealer, so their secrets are not the ones SignSealer holds | Press New address; SignSealer subscribes again and keeps the new secrets |
| **A guest got nothing** | No email on the booking, or no document fits the booking | The activity names the guest and the reason, or says nothing fitted |

## Lodgify's limits

Lodgify allows 750 requests a minute on its v2 API. SignSealer reads each booking once per change, and the property once more when the booking does not name it. Lodgify retries a delivery that is not answered 200, up to ten times, and may remove a subscription that keeps failing; SignSealer answers 200 as soon as a booking's delivery is recorded. Lodgify's API key reads and writes the whole account; SignSealer uses it only to read properties and bookings and to manage its own webhook subscriptions.

## Pausing and disconnecting

**Pause** keeps recording what arrives and works nothing until you resume. **New address** stops the old delivery address at once (and re-registers the webhook with the provider where SignSealer set it up). **Disconnect** revokes the connection's key, clears its credentials, removes the webhook from the provider where it can, and closes the address. The reservations and documents it made stay, with where they came from.

## From your own code

```
curl https://api.signsealer.com/v1/integrations -H "Authorization: Bearer $KEY"
curl https://api.signsealer.com/v1/integrations/$CONNECTION/events -H "Authorization: Bearer $KEY"
```

The first lists every provider with its status and your connections with their state; the second is what arrived from one connection and what became of it. Neither ever returns a credential, a delivery address or what arrived. Both need the `signing:read` scope. Connecting happens in the dashboard, where the provider confirms the credentials. See the [API reference](https://signsealer.com/docs/api).

[This page as Markdown](https://signsealer.com/docs/integrations/lodgify.md) Ask an AI about it: [ChatGPT](https://chatgpt.com/?q=Please%20read%20https%3A%2F%2Fsignsealer.com%2Fdocs%2Fintegrations%2Flodgify%20and%20explain%20it%20to%20me%20as%20a%20developer%20adding%20SignSealer%20to%20my%20application%3A%20what%20it%20covers%2C%20the%20calls%20involved%20and%20anything%20to%20watch%20out%20for.%20Use%20https%3A%2F%2Fsignsealer.com%2Fllms.txt%20for%20the%20rest%20of%20the%20docs%2C%20and%20cite%20the%20page%27s%20URL%20in%20your%20answer.) · [Claude](https://claude.ai/new?q=Please%20read%20https%3A%2F%2Fsignsealer.com%2Fdocs%2Fintegrations%2Flodgify%20and%20explain%20it%20to%20me%20as%20a%20developer%20adding%20SignSealer%20to%20my%20application%3A%20what%20it%20covers%2C%20the%20calls%20involved%20and%20anything%20to%20watch%20out%20for.%20Use%20https%3A%2F%2Fsignsealer.com%2Fllms.txt%20for%20the%20rest%20of%20the%20docs%2C%20and%20cite%20the%20page%27s%20URL%20in%20your%20answer.) · [Perplexity](https://www.perplexity.ai/search?q=Please%20read%20https%3A%2F%2Fsignsealer.com%2Fdocs%2Fintegrations%2Flodgify%20and%20explain%20it%20to%20me%20as%20a%20developer%20adding%20SignSealer%20to%20my%20application%3A%20what%20it%20covers%2C%20the%20calls%20involved%20and%20anything%20to%20watch%20out%20for.%20Use%20https%3A%2F%2Fsignsealer.com%2Fllms.txt%20for%20the%20rest%20of%20the%20docs%2C%20and%20cite%20the%20page%27s%20URL%20in%20your%20answer.) · [Google AI](https://www.google.com/search?udm=50&q=Please%20read%20https%3A%2F%2Fsignsealer.com%2Fdocs%2Fintegrations%2Flodgify%20and%20explain%20it%20to%20me%20as%20a%20developer%20adding%20SignSealer%20to%20my%20application%3A%20what%20it%20covers%2C%20the%20calls%20involved%20and%20anything%20to%20watch%20out%20for.%20Use%20https%3A%2F%2Fsignsealer.com%2Fllms.txt%20for%20the%20rest%20of%20the%20docs%2C%20and%20cite%20the%20page%27s%20URL%20in%20your%20answer.) · [Grok](https://grok.com/?q=Please%20read%20https%3A%2F%2Fsignsealer.com%2Fdocs%2Fintegrations%2Flodgify%20and%20explain%20it%20to%20me%20as%20a%20developer%20adding%20SignSealer%20to%20my%20application%3A%20what%20it%20covers%2C%20the%20calls%20involved%20and%20anything%20to%20watch%20out%20for.%20Use%20https%3A%2F%2Fsignsealer.com%2Fllms.txt%20for%20the%20rest%20of%20the%20docs%2C%20and%20cite%20the%20page%27s%20URL%20in%20your%20answer.)
