Get started

Setup guide

Connect Lodgify

Lodgify is a property management system with its own booking engine, so one connection brings in every property on the account and the bookings behind them — whether the guest came from Airbnb, Booking.com or your own website — and keeps them in sync with Levio's tax engine.

Five steps

From API key to first filing.

  1. 01

    Create an API key in Lodgify

    • Sign in to Lodgify as the account owner — the Public API is an account-level setting, not a per-property one.
    • Open Settings → Public API.
    • Generate a key and copy it straight away. Lodgify shows the full key once.
    • If the Public API section is missing, it is not enabled on your plan; ask Lodgify support to turn it on.
  2. 02

    Add the connection in Levio

    • Go to Settings → Connect a channel.
    • Choose Lodgify as the channel and give the connection a label, for example 'Lodgify — Gozo cottages'.
    • Paste the API key. Leave the API base URL blank unless Lodgify has given you a different host.
    • There is no account or agency id to find: a Lodgify key already identifies the account, so the key is the whole of the connection.
    • Click Connect channel. The key is encrypted with AES-256-GCM before it is stored and is never sent back to the browser.
  3. 03

    Run the first sync

    • Press Sync now on the new connection. Levio pulls every property on the account and the bookings changed since 1 January of last year.
    • Lodgify pages its API 50 records at a time; Levio walks the pages for you, so a large account needs nothing extra.
    • Each stay is run through the tax engine immediately: the matching rule, taxable nights and taxable guests are recorded.
    • Re-sync any time — amendments and cancellations update the existing records instead of duplicating them.
  4. 04

    Check the booking sources

    • Lodgify reports which channel each booking came from, and Levio keeps it: the Reservations table tags every stay Airbnb, Booking.com, Vrbo or Direct, with the Lodgify connection named underneath.
    • Filter the table by source to see, for example, only the stays a rule says the OTA already taxed.
    • The tag is in the bookings and payments CSV exports too, as the booking_source column.
    • A channel Levio does not recognise keeps Lodgify's own wording rather than being flattened away.
  5. 05

    Keep it in step

    • Levio polls this connection on a schedule, the same way it does Hostaway. A stay amended in Lodgify is picked up on the next sync rather than instantly.
    • Lodgify does publish a webhook API, and live updates for it are not wired up yet — the Live updates row in Settings stays off for Lodgify connections.
    • Press Sync now before you file if you want to be certain the period is complete.
    • The last sync time and any error are shown on the connection, so a key that has been revoked is visible rather than silent.

Troubleshooting

When the sync doesn't land

“Missing its API key”
The field was left blank and no LODGIFY_API_KEY server secret is set. Add the key to the connection, then sync again.
Lodgify request failed [401] or [403]
The key was revoked, copied incompletely, or the Public API is not enabled on the plan. Generate a new key in Settings → Public API and update the connection.
Properties sync but bookings don’t
Levio asks Lodgify for bookings changed inside the sync window. A stay that has not been touched in over a year will not come back — open and re-save it in Lodgify, or ask support to widen the window.
Guest counts look like adults only
Lodgify reports one headcount per room rather than an adult/child split, so Levio records everyone as an adult. Child exemptions in a tax rule therefore will not fire on Lodgify stays — deliberately, since guessing ages would under-collect.
Go to settingsConnecting Hostaway insteadConnecting Hostfully instead