Lodgify API
Lodgify exposes a REST Public API at api.lodgify.com in two versions, v1 and v2, covering properties, rates, availability, bookings, enquiries, quotes, payment links, message threads and webhooks, authenticated with an account API key sent in the X-ApiKey header.
Written from running this integration in production. Last checked against the Lodgify API on 11 November 2026.
Lodgify API report card
From Lodgify's own documentation. Checked on 11 November 2026.
- Base URL / API style
https://api.lodgify.com, REST and JSON, in two versions:/v2/…for most reads,/v1/…for most writes. source- Auth
- One account API key, from Settings → Public API, sent in the
X-ApiKeyheader. No token exchange. source - Rate limits
- 750 requests / minute on v2 and 600 / minute on v1; a 429 states the reason for the block. source
- Webhooks
- Subscribe, list and unsubscribe through
/webhooks/v1/…, one event and one target URL per subscription; events cover booking changes, rates and availability. source - Read / write coverage
- Read properties, rooms, rates, availability and bookings; create, update, decline, trash and restore bookings and enquiries; quotes, payment links, rate updates and availability changes. source
- Guest messaging
- v2 reads a message thread by id; v1 adds messages to a booking or an enquiry. source
- Sandbox / test account
- Not documented.
- Partner / marketplace programme
- Not documented.
- Restrictions worth knowing
DELETEon a booking moves it to the trash rather than cancelling it; the v1 booking update notes that not all fields can be updated. source
What the Lodgify API is
Lodgify’s Public API lives at https://api.lodgify.com and comes in two versions you use side by side. v2 reads properties, rooms, rates, availability, bookings and message threads. v1 is where most writes are: creating, changing, declining and restoring bookings and enquiries, quotes, payment links, rate updates, availability changes and webhooks.
Access is self-serve: the account’s API key is on the Public API page in Settings, with no token exchange and no expiry. Lodgify suits hosts who take direct bookings on a Lodgify website, so much of the API is about the inbox: bookings and enquiries, their status, quotes and payment links.
Conversations are the thin part. v2 reads one message thread by id; v1 adds messages to a booking or an enquiry in the Lodgify inbox. Through Repull, Lodgify threads are read, and replies are not sent through Lodgify.
How to get Lodgify API access
- 1.In Lodgify, open Settings → Public API. The account’s API key is shown there.
- 2.Send it in the
X-ApiKeyheader on every request tohttps://api.lodgify.com. There is no token to fetch and nothing to refresh. - 3.Use
/v2/…paths for most reads and/v1/…paths for most writes. The same key works on both.
If the Public API page is missing, check the Lodgify plan with Lodgify support before building anything.
What will bite you
From running this integration in production and reading the vendor's documentation line by line.
Two API versions, two shapes of the same booking
You read a booking with GET /v2/reservations/bookings/{id} and write it back with PUT api.lodgify.com/v1/reservation/booking/{id}, which takes the v1 booking-details object returned by GET api.lodgify.com/v1/reservation/booking/{id}. Expect two models of a booking in your code, and Lodgify notes that “not all fields can be updated” through the v1 update.
DELETE moves a booking to the trash; it does not cancel it
DELETE api.lodgify.com/v1/reservation/booking/{id} “moves a booking to the trash”, from where it can be restored. A cancellation is a status change: PUT api.lodgify.com/v1/reservation/booking/{id}/decline. Use DELETE to cancel and the booking goes to the trash instead of showing as declined.
Status changes are separate calls
Booked, tentative, declined and open each have their own endpoint (/book, /tentative, /decline, /reopen), and /book is the one that “updates the availability calendar accordingly”. Updating a booking does not change its status; check the status after creating one, and move it explicitly if it is not what you expected.
Rates and availability need a room type, even for one home
The calendar is addressed by property and room type: “most rentals on Lodgify have only a single room type id”, but you still look that id up before you can read or write a single home’s rates. Through Repull, Lodgify bookings are single-room; a group booking is refused.
Poll from your last sync point, or every booking looks new
Most integrations poll as well as subscribe to webhooks, to catch anything a webhook missed. A poll that ignores its last sync point gets the whole booking list back every time, and code that diffs it treats every booking as new or cancelled. In production we saw 13 bookings turn into about 1,260 change events an hour before the poll filtered on the last update.
Rate limits differ by version
Lodgify publishes separate limits: 750 requests a minute on v2 and 600 on v1. Going over returns a 429 with the reason for the block, so a sync that mixes versions has two budgets to track.
What it costs to keep working
Lodgify is quick to connect: one key, no token exchange. What you maintain is the seam between two versions.
- •Two booking models, v1 and v2, kept in step as Lodgify changes either.
- •A status machine: booked, tentative, declined, open and the trash, each with its own call and its own effect on availability.
- •Polling and webhooks together, deduplicated, so every change is processed once.
- •A key per client to store, and to replace when the client regenerates it.
The same job, both ways
Lodgify directly
# One key, sent on every call. Reads mostly on v2.
curl -s 'https://api.lodgify.com/v2/reservations/bookings?page=1&size=100' \
-H 'X-ApiKey: YOUR_LODGIFY_KEY'
# Writes mostly on v1. Cancelling is a status change:
# DELETE would move the booking to the trash instead.
curl -s -X PUT 'https://api.lodgify.com/v1/reservation/booking/BOOKING_ID/decline' \
-H 'X-ApiKey: YOUR_LODGIFY_KEY'Through Repull
# Connect once with the same key.
curl -s -X POST 'https://api.repull.dev/v1/connect/lodgify/credentials' \
-H 'Authorization: Bearer sk_live_YOUR_KEY' \
-H 'Content-Type: application/json' \
-d '{"credentials": {"apiKey": "YOUR_LODGIFY_KEY"}}'
# One version, one shape: reservations from Lodgify and every other
# connected PMS and channel.
curl -s 'https://api.repull.dev/v1/reservations?limit=100' \
-H 'Authorization: Bearer sk_live_YOUR_KEY'
# Cancelling declines the booking in Lodgify; it is not trashed.
curl -s -X POST 'https://api.repull.dev/v1/reservations/RESERVATION_ID/cancel' \
-H 'Authorization: Bearer sk_live_YOUR_KEY'Why use Repull for Lodgify
Your second client will not be on Lodgify
If you build for one Lodgify account and always will, use the Public API directly: one key, no OAuth, and Repull would be a layer you do not need. The cost arrives with the next system.
One reservation shape across every system
A Lodgify booking, an OwnerRez booking and a Hostaway reservation come back from GET /v1/reservations with the same fields, platform naming the channel. No v1-versus-v2 mapping on your side.
Cancels that cancel
POST /v1/reservations/{id}/cancel declines a Lodgify booking, never trashes it, and the same call cancels on the other PMSs that allow it. Where one does not, Repull answers 422 pms_write_unsupported naming it.
Every system authenticates differently
Lodgify is one key. Smoobu signs every request with a key, a secret and a nonce. Beds24 swaps an invite code for refresh tokens. Guesty allows five tokens a day. You keep one Repull key.
Channels next to the PMS
Some clients have no PMS at all. The same Repull key connects Airbnb, Booking.com and Vrbo directly, and more, alongside Lodgify accounts.
Connect Lodgify through Repull
Create a key, connect a Lodgify account with the credentials Lodgify issues, and read reservations in the same shape as every other system you support.
Frequently asked questions
Does Lodgify have an API?
Yes. Lodgify’s Public API at https://api.lodgify.com covers properties, rooms, rates, availability, bookings, enquiries, quotes, payment links, message threads and webhooks, across two versions (v1 and v2). An account holder copies the API key from Settings → Public API.
How do I get a Lodgify API key?
In Lodgify, open Settings → Public API; the account’s key is shown there. Send it in the X-ApiKey header on every request. There is no token exchange and no expiry.
What are the Lodgify API rate limits?
Lodgify publishes 750 requests per minute on v2 and 600 per minute on v1. Going over returns HTTP 429 with the reason for the block.
Can I send guest messages through the Lodgify API?
Lodgify’s v2 API reads a message thread by id, and its v1 API adds messages to a booking or an enquiry in the Lodgify inbox. Through Repull, Lodgify threads are read and replies are not sent through Lodgify; connect the channel directly to reply to Airbnb, Booking.com or Vrbo guests.
How do I cancel a booking with the Lodgify API?
Decline it: PUT api.lodgify.com/v1/reservation/booking/{id}/decline sets its status to Declined. DELETE api.lodgify.com/v1/reservation/booking/{id} does not cancel; it moves the booking to the trash, from where it can be restored.
Does Lodgify have webhooks?
Yes. You subscribe through the v1 webhooks endpoints, one event and one target URL per subscription, for booking changes, rate changes and availability changes, and you can list and unsubscribe them through the API.
Can I use Lodgify and Repull together?
Yes. Repull connects with the same API key and changes nothing inside Lodgify. You read through Repull’s unified schema and can still call Lodgify directly for anything Lodgify-specific.
The other systems Repull connects
Reference
Auth Type
API Key
Required Fields
apiKeySupported Operations
Connection Guide
In Lodgify, open Settings → Public API and copy the API key shown there. Send it as apiKey.
Notes
- • One account API key, sent in the X-ApiKey header
- • Two API versions used side by side: v2 for most reads, v1 for most writes
- • Guest message threads are read through Repull; replies are not sent through Lodgify
- • Built-in website/booking engine