Practical guide

API vs iCal: what actually needs to sync?

Last materially reviewed 2026-09-19

Quick answerTreat an availability feed and a broader channel integration as different tools; verify the data carried by your exact connection.
What to know

Start with the data, not the acronym

Write down what you need exchanged: occupied dates, nightly prices, stay restrictions, guest messages or reservation changes. An integration label alone does not answer that list. Lodgify’s documentation distinguishes calendar-feed synchronization from broader API connections. The useful question is which fields are supported for your specific channel and direction, not whether one acronym sounds more professional.

What to know

Know the calendar-feed boundary

An iCal feed primarily communicates calendar events or availability information. Do not assume it transfers your rate rules, guest conversation or payment state. Refresh timing can differ between systems. A date appearing correctly in one calendar is therefore not proof that another channel has received the latest update or that a guest-facing price is correct.

What to know

Do not turn API into a guarantee

A direct integration may exchange more data, but supported fields, account requirements and failure behavior still matter. Ask where an error appears and what the provider recommends when updates are delayed. No connection removes the need for a recovery path. We have not measured synchronization speed or incident rates for the products discussed on this site.

What to know

Make a connection worksheet

For each channel, record the supported connection type, data direction, authoritative editor and verification step. Include a named person who checks problems. Keep private feed addresses and account credentials out of public documents. Use the vendor’s supported onboarding process; do not connect a live calendar merely to experiment with an integration whose behavior you do not yet understand.

What to know

A practical data-boundary exercise

Make two rows for the same fictional property: dates and rates. Ask which connection transfers each row and how the receiving channel confirms it. If an availability feed carries the first but not the second, keep the rate workflow separate. This demonstrates why a visible synchronized calendar cannot stand in for evidence that the full guest-facing quote is synchronized too.

Continue when useful

Next: Map who controls dates, rates and messages

Each important field needs an authoritative editing location and a known verification path.

Open Map who controls dates, rates and messages →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Lodgify iCal integration — Merchant documentation · lodgify.com · Merchant-controlled · checked 2026-09-19
  2. Lodgify API integration explanation — Merchant documentation · encyclopedia.lodgify.com · Merchant-controlled · checked 2026-09-19