What changed in the Lodgify Public API this quarter
Lodgify shipped two meaningful changes to their Public API in Q2 2026 that affected every Blastnes module. Neither was a surprise — both had been on Lodgify's roadmap for months — but both required real work on our side to absorb quietly. Since a few hosts have written in asking whether they need to do anything, the short answer is no. The longer answer is below.
1. New availability endpoint (/v2/availability)
The old /v1/availability endpoint returned a flat calendar of blocked and free nights per unit. The new /v2/availability adds a "reason" field on every blocked night — booked, closed by owner, blocked by cleaning, held by tentative reservation. This is genuinely useful, because previously Sync Sentinel and Group Enquiry Router had to guess.
We migrated every module to /v2/availability in a two-week rollout, running both endpoints in parallel for a week to compare outputs. Zero discrepancies. The old endpoint stays live at least until end of Q1 2027 per Lodgify's public deprecation schedule.
2. Deprecated inventory sync webhook
The inventory-sync-completed webhook, which pinged every subscriber whenever a channel finished pushing rates and availability, is going away by 30 September 2026. Lodgify's rationale is fair — the webhook was a firehose that most integrators didn't want. In its place is a polled endpoint (/v2/sync-status/{channel}) that returns the timestamp and status of the last push per channel.
Sync Sentinel is the module most affected. We rebuilt it around the polled endpoint, cache-aware, so we still detect a stalled channel within 90 seconds without hammering Lodgify's rate limiter. For hosts, nothing changes — you still get the same alerts on the same channels, only the plumbing is different.
3. Minor: new rate-plan metadata field
Rate plans in Lodgify now carry an optional "corporate" boolean, so operators can flag which rates are meant for the Corporate Traveller Portal versus regular OTA distribution. If you use our Corporate Traveller Portal module, we now automatically respect that flag — no more accidentally showing your public rate to a company client whose portal expects the corporate one.
What you need to do
Nothing. Every Blastnes module was migrated to the new API surface before Lodgify started sending deprecation warnings. If you see a warning in the Lodgify UI about the old webhook, it means Lodgify still has other integrations subscribed — it does not come from us.
If you'd like to see the full change log for our modules, it's in the account under Settings → Change log. And if you have questions about a specific module's API footprint, write to me directly: lucas@blastnes.org.