API vs iCal: what actually needs to sync?
Read the guide →Guide preview
Treat an availability feed and a broader channel integration as different tools; verify the data carried by your exact connection.
Map availability, rates, messages and checkout before changing a live connection.
Understand API versus iCal, then plan the supported migration and verification.
New to the topic? Begin with the first guide. Otherwise, go straight to the question you need to answer.
Treat an availability feed and a broader channel integration as different tools; verify the data carried by your exact connection.
Each important field needs an authoritative editing location and a known verification path.
Confirm supported account behavior and property mapping before changing a live sales channel.
Verify the exact listing, data responsibilities and payment arrangement rather than assuming every channel behaves alike.
Preserve a useful existing site unless replacing it solves a demonstrated problem.
Check clarity, property identity and failure recovery without making a real reservation or payment.
Reconcile records and responsibilities before retiring the old system; do not treat import success as complete migration.
Choose the supported source of each price and restriction; do not edit every dashboard until numbers happen to match.
A blocked date, a cancelled booking and a removed calendar event are not necessarily the same operation.