Revenue and reports

Sync Airbnb and Booking calendars: iCal or API?

iCal shares blocked dates with delays; an API can also manage rates, restrictions and reservations, depending on the integration. Choose according to your booking risk, then verify bookings, changes and cancellations before expanding the setup.

Sixto team21 min read

Aparthotel photo: revenue and reports

Choose by booking risk, not just unit count

iCal shares blocked dates, with delays. An API connection through a channel manager can manage availability, rates, restrictions and reservations, depending on what each integration supports. Neither option removes every risk of overbooking.

If you want to sync Airbnb and Booking calendars for the same apartment in Colombia, start with how you accept and manage bookings. One or two units do not automatically make iCal suitable. A single apartment listed on two channels can still receive conflicting reservations.

Before choosing, answer these questions:

  • How far ahead do guests usually book?
  • Do you accept last-minute bookings or same-day arrivals?
  • Do departures and arrivals fall on the same day?
  • How many channels do you sell through, alongside direct bookings?
  • Who can check and protect availability when you are unavailable?

iCal may be enough if guests book ahead, you can limit sales close to arrival, and someone checks the dates. If you need to coordinate frequent changes, several channels or last-minute sales, assess an API connection and verify its supported functions.

Tip: Choose based on how long a mismatch could go unnoticed, not just how many apartments you manage.

This is not only a technical decision. It also depends on who takes responsibility when the connection fails.

What an iCal link carries and what it leaves out

For inventory control, treat iCal as an exchange of blocked dates, not complete reservations. It does not synchronise prices, minimum stays, arrival restrictions or an operational guest record. Changing a rate on one channel does not send that change through the calendar link.

A calendar file may contain event titles, identifiers or other metadata. Those details are not the same as a complete, usable reservation record. Do not rely on event text to arrange payments, identify guests or send arrival instructions.

Export and import are separate directions

Exporting means a channel provides a link to its calendar. Importing means another channel reads that link and applies the blocks it supports. Importing does not set up the return journey. If Booking.com imports an Airbnb calendar, Airbnb does not automatically receive the Booking.com calendar.

To understand an existing connection:

  1. Identify which channel publishes the link and which channel imports it.
  2. Check separately whether a connection exists in the opposite direction and whether both channels support it.
  3. Compare the blocked dates at the destination with the source. Seeing the calendar name does not prove its events are current.

Worked example: occupied nights in apartment 402

In this illustrative example, apartment 402 has a booking arriving on June 12 and departing on June 15. The occupied nights are June 12, 13 and 14. June 15 is the departure date, not another occupied night under that booking.

Check how each platform displays that boundary. Also check the time zone used to interpret dates and times. If a block appears shifted, investigate those settings before manually adding another night. Commercial availability does not establish that the apartment is ready for the next guest, either.

Each platform controls its refreshes

Each platform decides when it reads external calendars. Check the current official Airbnb and Booking.com help documentation for import and refresh conditions, then measure what happens in your setup. Do not assume a universal refresh interval.

Tip: Refreshing your screen does not prove that the channel has imported the calendar again. Check the specific block at the destination and record when you observed it.

A visible calendar shows that something has loaded. It does not prove the entire connection works.

Manual control, iCal or API: compare the trade-offs

Choose according to what needs to move between systems and who can monitor it. Keeping a record, sharing blocked dates and managing sales across channels are different jobs. None of these options replaces checking that published availability matches what you can actually sell.

Option Best for Strengths Watch-outs
Manual control with paper or a spreadsheet Operations where you can check and update every channel whenever something changes A straightforward record of bookings, decisions and outstanding work Requires work in each channel. A spreadsheet supports auditing but does not automatically close inventory
iCal Sharing blocked dates when you can supervise delays and manage other settings separately Reduces repeated manual blocking through supported import and export directions Does not manage rates or restrictions. Imports need checking, with safeguards for bookings close to arrival
API through a channel manager or PMS Operations needing central control of several commercial flows Can exchange availability, rates, restrictions and reservations, depending on the integration Requires compatibility, permissions and mapping checks. Does not guarantee instant updates or prevent every overbooking

A channel manager distributes commercial information between sales channels. A PMS manages property operations and reservations; it may include a channel manager or connect to one. Having a PMS does not prove your distribution is connected.

Direction matters too. Sending availability to a channel does not prove that bookings flow back. Receiving bookings does not establish that you can publish rates or restrictions. Check each flow separately for Airbnb and Booking.com under their current connection conditions.

1. Ask for a demonstration you can verify

  1. List your requirements: receiving bookings, sending availability, changing rates or applying minimum stays. Separate essential functions from optional ones.
  2. Ask to see each function in the relevant channel, not just the provider dashboard. Check what goes out, what comes back and how a rejection is reported.
  3. Request evidence of monitoring: transmission status, visible errors and the support process. A sent message does not prove the change is published.
  4. Cross-check current compatibility in official Airbnb and Booking.com help resources and the provider documentation. Verify the scope of any recognition or certification mentioned.

Tip: Choose proven capabilities, not the word “integration”. Ask to see the full journey of a change.

To decide, ask: can you keep every channel updated manually? Do you only need blocked dates, or also rates and restrictions? Who will spot a failure? If you cannot give an operational answer, change the connection or limit your exposure before expanding sales.

Set up iCal without leaving gaps

1. Match physical units to listings

List your physical units, their listings and any existing calendar connections before copying links. In an illustrative example, apartment 402 has an Airbnb listing and a Booking.com listing. They sell the same apartment, not two available units.

Identify each route separately: Airbnb to Booking.com, then Booking.com to Airbnb. Check whether a connection already covers that route. Adding another without checking can duplicate events or create confusing loops.

2. Check what each channel supports

Use the current official Airbnb and Booking.com help documentation to confirm whether your listings support calendar export and import, and which events they export. Avoid relying on menu instructions from an old tutorial.

Check manual blocks and direct bookings specifically. Do not assume a channel exports blocks it originally imported. If you take bookings outside the platforms, decide where to record them and how to close the affected dates on every listing. A chain of calendar links is not proof that those dates will reach every channel.

3. Connect each supported direction

Get the export link from the source listing and import it into the matching destination listing. Give the connection a clear name, such as “402, Airbnb to Booking.com”. Then configure the reverse route if both channels support it.

Record the source and destination of each configured link so the next shift can identify it.

Tip: Verify each direction separately. Seeing an imported calendar does not prove the other channel is receiving your blocks.

4. Verify dates and assign ownership

Compare occupied and available dates in each channel, not just on the screen where you pasted the link. Check how manual blocks and direct bookings appear as well. Record the result without copying the iCal address into the log.

Assign an owner and a backup. Decide when they will check the connection and who will manually close affected dates through each channel’s authorised controls if availability differs. Verify those closures before treating the inventory as protected.

Setup checklist

  • Every listing matches the correct physical unit.
  • Every supported direction has a clear source, destination and name.
  • Exported events, duplicates and loops have been checked.
  • An owner, backup and manual closure procedure are defined.
  • Links are stored with restricted access, never in public chats or the shared log.

Treat calendar links as restricted-access information. For privacy practices in Colombia, consult the guidance and criteria published by the Superintendencia de Industria y Comercio.

Connect an API and verify mapping before selling

Authorising a connection does not prove that your inventory is mapped correctly. Before opening sales, establish what each unit represents, which system can change it and how reservations reach the receiving system.

1. Check compatibility and authorisation

Consult the provider’s current documentation and the channel’s official sources. Confirm which property setup, connection type and functions the integration supports. If the provider holds a certification or recognition, check its scope. That status does not establish that every feature is available to your account or guarantee trouble-free operation.

Authorise access through the supported controls and review permissions. Permission to receive reservations is not the same as permission to update availability, rates or restrictions.

2. Map the inventory you actually sell

Match these elements using their identifiers:

  1. The property in your system and on the channel.
  2. The physical unit and its room type.
  3. The listing selling that unit or category.
  4. The available inventory each reservation consumes.
  5. The applicable rate plan and its rules.

For categories containing several units, confirm how bookings reduce shared inventory. Matching names alone are not proof of a correct relationship.

Worked example: two listings, one apartment 402

In this illustrative example, you list apartment 402 on Airbnb and Booking.com. You have two listings, but only one physical unit. A reservation must consume the corresponding availability across both channels. Assigning independent inventory to each listing could leave the same apartment available for a second sale. Verify the relationship before enabling sales.

3. Assign control of each field

Document where you manage availability, rates and restrictions. Different systems may control different fields, depending on the integration. Do not let two systems overwrite the same field without a clear rule.

Check new reservations, modifications and cancellations. Also verify minimum stays and any supported stop-sell, arrival or departure restrictions. Unsupported functions need a separate control.

Tip: Verify the result on the channel, not just the provider’s successful-connection message.

4. Protect inventory during the changeover

Keep affected inventory protected while reconciling existing reservations against the new system. Establish which bookings are imported, which need additional entry and how later changes will arrive. Avoid creating duplicates through manual entry.

Retire previous connections in a controlled sequence after verifying continuity. Do not disconnect everything first and configure the replacement afterwards.

  • Property, unit and rate-plan identifiers checked.
  • Controlling system and write permissions documented.
  • Existing reservations reconciled without omissions or duplicates.
  • Reservations, changes, cancellations and restrictions verified.
  • Previous connections retired without a gap in control.
  • A named person will authorise reopening based on evidence.

Test bookings, changes and cancellations both ways

1. Choose a safe testing method

Before peak season, check the testing methods supported in Airbnb and Booking.com’s official help and your provider’s documentation. Use a test environment where available. Do not create fictitious bookings to exercise the connection. If an authorised real booking is necessary, review the terms, potential charges and cancellation conditions first. Do not assume cancellation will be free.

Assign someone to trigger each event and someone to verify the result. Choose a unit and controlled dates without putting existing reservations at risk.

2. Run the matrix in each direction

Test from each channel to the connected system and onward to other channels, wherever those flows are supported. With an API connection, also test updates sent by the system responsible for inventory. For iCal, mark rates and restrictions as out of scope, not passed.

Event Origin Expected result Evidence Owner Pass criterion
Booking Each channel Occupied nights close at destinations Reference and timestamped screenshots Front desk No conflicting bookable availability
Date change Booking channel New nights close; previous nights reopen where appropriate Dates before and after Front desk Matches the amendment
Cancellation Booking channel Dates reopen unless another block applies Status and availability search Front desk Consistent, explained result
Manual block Authorised system Closure reaches destinations supporting that flow Block record Administrator Intended nights closed
Departure Test dates Final occupied night and departure date handled correctly Search across consecutive nights Front desk No extra night blocked
Restriction Authorised API source Supported minimum stay or closure applied Qualifying and nonqualifying searches Administrator Selling behaviour matches the rule

3. Check what a guest can actually buy

Record the event time and observation time, using the same time zone. Inspect both the connected systems and guest-facing availability, with equivalent dates and occupancy.

Distinguish three stages: message receipt, update acceptance and publication for sale. An acknowledgement of receipt does not establish the other two. Your observed elapsed time does not identify the exact propagation time or promise future speed.

For example, a closure recorded for illustrative unit 402 is not enough if a guest can still book those nights on the destination channel.

Tip: Pass the test on the published result, not just a “sync successful” message.

4. Keep evidence and repeat

  • Both supported directions checked.
  • Discrepancies investigated before approval.
  • Test blocks removed in a controlled way.
  • Evidence and responsible person recorded.
  • Tests repeated after relevant changes to connections, permissions, mapping or rules.

Two worked scenarios: when iCal fits and when it does not

Illustrative scenario 1: one apartment, two channels, advance bookings

You list one apartment on Airbnb and Booking.com. Guests usually book well ahead, and you can check both channels after each change. Your operation does not depend on selling gaps just before arrival.

iCal can be enough, provided you confirm that both channels support the required exchange in each direction. Importing Airbnb into Booking.com does not set up the return connection.

In this example, you run the arrangement as follows:

  1. Maintain both supported connections and check that a booking blocks the correct nights on the other channel.
  2. When you accept a direct booking, protect those dates on both channels and verify the result. Do not assume an imported block will be exported again.
  3. Choose a cutoff for accepting bookings close to arrival based on your ability to supervise them. Set that rule in the relevant controls: iCal does not carry it.
  4. If you cannot monitor a close-in sale, manually close the affected inventory and check that the closure is visible.

Decision: keep iCal while this checking workload remains manageable. Residual risk: another booking can arrive before the block is imported. Evidence needed: successful checks in both directions, direct bookings accounted for, and recorded discrepancies. A small portfolio does not replace these checks.

Illustrative scenario 2: apartment 402 checks out at 10:30 and has another arrival

Apartment 402 has a 10:30 checkout and an arrival scheduled for the same day. During the night shift, a last-minute Airbnb booking comes in for that arrival while Booking.com still shows availability. The night receptionist does not wait for the next iCal import. They protect the affected nights through authorized controls and check what a buyer can still book.

Next, they reconcile the new booking against existing reservations. If another confirmed reservation covers the same nights, they escalate to the responsible manager before offering a solution. They do not delete bookings or promise early access.

The housekeeping lead receives the scheduled 10:30 departure and the incoming arrival details. They arrange cleaning and report when the physical inspection is complete. Closed inventory does not mean a clean apartment. Reception checks readiness separately before authorizing entry.

Tip: keep commercial availability and housekeeping readiness as separate controls. No connection replaces confirmation that the apartment is ready.

Decision: assess an API connection through a channel manager with verified support for these channels and functions. It can reduce manual work and exposure during updates, but it cannot guarantee instant delivery or eliminate failures. Residual risk: connection errors, inventory mistakes and an unprepared apartment. Evidence needed: a visible closure on the other channel, a reconciled reservation and housekeeping confirmation before entry.

What to do when dates disagree or bookings overlap

When you find a mismatch, protect the affected inventory first. Investigate the cause next. An updated screen does not prove that another channel has received and published the change.

1. Contain the problem and preserve evidence

Use authorised controls to close sales temporarily for the affected unit and dates. Check the closure on every channel, including the availability a prospective guest can actually book. Do not assume it has reached the channels because your main system shows it.

Keep booking references, stay dates, the event time and your verification time. Save relevant error messages and screenshots in a restricted-access incident record. Do not delete reservations or reconnect repeatedly. You could lose evidence and introduce more problems.

2. Trace where the change stopped

Follow the event from its source to the channel showing the mismatch:

  1. Identify where the booking, amendment or cancellation originated and confirm its current status there.
  2. For iCal, check that the link belongs to the correct listing, that the destination imports it in the required direction, and what update information the destination provides. Refreshing a screen does not prove a fresh import.
  3. For an API connection, check authorisation, write permissions and the mapping of units, inventory and rate plans. Review available error messages.
  4. Distinguish receipt, acceptance and publication of the update. Tell channel or provider support which stages you can verify and which remain unknown.

3. Restore availability without removing valid protections

A cancellation is not an instruction to reopen dates immediately. Look for another booking, manual blocks, sales restrictions or a unit that remains out of service.

Worked example: apartment 402 stays closed

In this illustrative example, a reservation for apartment 402 is cancelled, but a manual maintenance block remains. The receptionist confirms the cancellation and finds the block. Before removing it, they check with the person responsible for maintenance. If work remains unfinished, the closure stays. If work is complete, they remove only the authorised block and check the resulting availability on both channels.

Tip: A closed date may be correct. Find out what is keeping it closed before releasing it.

4. Escalate overlapping bookings and verify reopening

If two confirmed reservations cover the same unit and nights, contact the operational lead and support for the affected channels. Check real alternatives, their terms and who can authorise them. Tell guests only confirmed facts and when to expect the next update. Do not blame a platform or promise unapproved compensation.

Separate containment, recovery and correction: stop further sales, resolve affected bookings, then fix the cause. Reopen only with authorisation, reconciled inventory and verifiable evidence that the corrected availability appears on the affected channels.

Keep a useful sync log and measure reliability

Record each check with an internal reference, its outcome and the person responsible for any follow-up. Leave out guest names, contact details and iCal links. Your log should support decisions, not merely prove that someone opened a calendar.

Copyable monitoring template

The rows below are illustrative examples. Replace them with your own events and include the date and time zone with recorded times. Under “Closure”, record evidence of the fix rather than simply writing “done”.

Unit Event or internal reference Source Event time Check time Expected result Observed result Owner Action Closure
402 Block B01 Airbnb 09:00 09:12 Nights closed on Booking.com Nights closed Front desk Save evidence Closed: availability verified
403 Cancellation C02 Booking.com 10:00 10:15 Dates reopen unless other blocks remain Dates still closed Administration Review blocks and connection Open
404 Mapping error M03 Channel manager 11:00 11:08 Linked listing closes Different listing closed Operations manager Protect inventory and review mapping Open

Track four measures without overstating the results

  • Observed delay: subtract the event time from the check time. This interval shows when you verified the result, not exactly when it reached the destination. If the calendars still disagree, do not record it as a completed sync time.
  • Discrepancies per check: divide checks that found a mismatch by all checks performed during the same period. Keep both counts and apply a consistent definition of a check.
  • Open incidents: count issues without verified closure at the reporting cutoff. Repeated checks of one unresolved problem are not separate incidents.
  • Resolution time: measure from detection to a verified fix. A support reply is not evidence that the problem is resolved.

Tip: keep test records separate from live operational records. Combining them can hide the failures that affect actual sales.

Compare periods with similar operating conditions. Note any changes to connections or selling rules alongside the results. A cluster of mismatches around last-minute bookings may call for closer supervision or different booking rules. Repeated mapping errors or missing functionality may call for a configuration review or another connection method.

Do not adopt a universal pass threshold. Use your exposure and recorded evidence to decide what needs to change. The point is not to collect more rows. It is to know where your current setup needs attention.

Schedule checks and prevent recurring mistakes

Give every check an owner and name a backup. Front desk owns availability, administration maintains connections, and the housekeeping lead confirms physical readiness. You can combine roles in a small team, but do not leave responsibilities implied.

The schedule below is illustrative. Adapt it to your shifts, channels and exposure to last-minute bookings. It is not an official checking frequency.

Trigger Check Owner Evidence
Start of shift Compare channel availability and outstanding issues Front desk Timestamped record of differences
Booking close to arrival Confirm dates close on other channels and check physical readiness Front desk and housekeeping lead Channel checks and cleaning status
Cancellation Check whether dates should reopen and whether other blocks remain Front desk Internal reference and observed availability
Connection change Verify directions, mapping and the system authorised to make edits Administration Test results and unresolved items
Shift handover Transfer open incidents and temporary sales closures Outgoing and incoming receptionists Named owner and recorded next action

Mistakes to catch in your routine

At handover, identify which direction has a mismatch and who must check it again. An incident without an owner remains unresolved even if no warning appears.

Avoid editing the same setting from several systems without a designated source of truth. Include direct bookings in availability control. Check that two listings for one apartment do not become two sellable units.

Tip: Available dates do not mean a clean apartment. Verify commercial inventory and physical readiness separately.

When to pause sales and who can reopen them

Temporarily stop selling the affected unit and dates through authorised controls if dates disagree, inventory is uncertain, or readiness for an arrival cannot be assured. Verify the closure on every channel rather than assuming it propagated.

Before reopening:

  • Front desk has reconciled bookings and availability.
  • Administration has checked the connection if a technical fault occurred.
  • The housekeeping lead has confirmed readiness where relevant.
  • Your designated decision-maker, or their backup, has authorised reopening with recorded evidence.

Make that authority explicit before the next shift takes over. An unresolved closure needs an owner, not just a handover comment.

Your practical plan for dependable calendar sync

1. Set the scope and assign ownership

  1. Match every physical unit to its listings and channels. Include direct bookings in your inventory review.
  2. Choose iCal or API based on what you need to transmit and the risk you can monitor. Document what the connection leaves out.
  3. Assign an inventory owner and an out-of-hours backup. Specify who can stop sales and who can authorise reopening.

2. Approve one pilot unit before expanding

  1. Configure a single unit, for example, apartment 402. Protect its inventory during the transition and retain existing booking references.
  2. Test bookings, changes and cancellations both ways using methods supported by the channel and provider. Check blocks and, where supported, restrictions too.
  3. Reconcile existing reservations against available nights. Inspect both the connected systems and the availability a guest can actually book.
  4. Extend the setup only when you have evidence that the pilot passed. If differences remain unexplained, keep affected inventory protected and resolve them before proceeding.

Tip: Do not approve a connection because its status says active. Approve it because you can verify its results.

3. Copy this approval checklist

  • Physical units matched to listings without duplicating inventory.
  • Connection scope and limitations documented.
  • Tests verified in both directions.
  • Existing reservations reconciled.
  • Inventory owner and backup briefed.
  • Evidence reviewed before expansion.

Owner: [name or role]
Date: [date]
Outstanding items: [details and owner]

Before signing off, answer: Who controls inventory? What does the connection not transmit? How will you detect a failure? Who protects sales outside normal working hours? If an answer is missing, the setup is not ready for operational approval.

Practical operations guidance, not legal or tax advice.

ShareWhatsAppLinkedInX