The API Report CardAPI Index
Lodgify

Lodgify API

lodgify.com

Lodgify publishes a REST v2 API covering properties, rates, bookings, and messaging, with API-key or OAuth 2.0 auth and a 750 calls/min limit. Access is plan-gated: Starter customers are locked out, and partner OAuth requires approval. The surface still splits across legacy v1 and v2.

Last verified: July 2026Hospitality & Travel
API GRADE
C
VERIFIED JUL 2026

SCORECARD

ExistenceGOODA documented public REST API (v2) returning JSON, with published rate limits and webhook support.
AccessPOORPlan-gated: Starter customers get little or no API access, and partner OAuth clients require Lodgify approval.
CoverageMIXEDProperties, rates, availability, bookings, and messaging are covered; OTA channel sync state is only partially exposed.
AuthGOODLong-lived API key header for first-party use, full OAuth 2.0 for approved partner integrations.
Docs & DXPOORNo official SDK, no sandbox without an account, and webhook retry semantics are lightly documented.
StabilityMIXEDSplit across legacy v1 and v2 with incomplete parity; some operations remain v1-only.
Supergood: Lodgify has an API, with gaps. We cover what it's missing: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Lodgify scores C on the API Report Card. Lodgify publishes a REST v2 API covering properties, rates, bookings, and messaging, with API-key or OAuth 2.0 auth and a 750 calls/min limit. Access is plan-gated: Starter customers are locked out, and partner OAuth requires approval. The surface still splits across legacy v1 and v2.

Tried to integrate with Lodgify?
SOURCES
API access is plan-gated, Starter customers cannot use the API even though their reservations live in Lodgify lodgify.com β†—
Documented 750-calls-per-minute rate limit; some users report tighter limits in practice and 429 responses without clear backoff guidance docs.lodgify.com β†—
OAuth and partner-marketplace access requires Lodgify approval; independent developers and internal teams cannot self-serve a multi-tenant integration docs.lodgify.com β†—
API surface is split between legacy v1 and current v2 endpoints; feature parity is not complete and some operations are still v1-only docs.lodgify.com β†—
Webhook reliability and delivery retry semantics are lightly documented; integrators report needing to poll endpoints as a fallback rollout.com β†—
Channel-manager state (Airbnb/Booking.com/Vrbo sync status, last-sync timestamps, sync errors) is partially exposed; troubleshooting OTA sync issues still requires the Lodgify UI boldertechnologies.net β†—
Per-property rate plans, seasonal pricing rules, and discount stacking are exposed but the data model is non-obvious; integrators frequently misprice when round-tripping rates apitracker.io β†—
Promised 24-hour phone support but customers report response rates well below promise; reliance on email replies that take 24–48 hours or more lodgify.pissedconsumer.com β†—
UI described as clunky, unintuitive, and dated; website editor and unified inbox less customizable than expected trustpilot.com β†—
Auto-messaging bugs reported to remain unresolved for months even after video documentation submitted to support lodgify.pissedconsumer.com β†—
'No refunds after 14 days' policy enforced strictly; customers report being unable to recover fees after 8+ weeks of unresolved technical issues trustpilot.com β†—
Integration/onboarding 'didn’t go well as promised'; technical team reportedly slow to resolve channel-sync and OTA-connection issues trustpilot.com β†—
Capterra reviewers cite cumbersome reporting and limited financial/owner-statement depth versus Hostaway/Guesty capterra.com β†—
Starter plan adds a 1.9% booking fee on top of subscription, effective cost on small portfolios is higher than the headline $16/mo/property lodgify.com β†—
Channel-sync lag and occasional double-bookings reported when OTAs return updates faster than Lodgify can ingest them capterra.com β†—