Black Friday
Skip to documentation content

Channels & Calendar

Configure Booking.com and Agoda under Advanced Integration

Pro retains the existing Booking.com/Agoda API module alongside iCal. These are different integration protocols with different credentials, mapping and reservation semantics; adding an iCal URL does not configure an API account.

Pro retains the existing Booking.com/Agoda API module alongside iCal. These are different integration protocols with different credentials, mapping and reservation semantics; adding an iCal URL does not configure an API account.

Choose the intended owner

Use the API module only when the hotel has the provider access and credentials required by that integration. Verify entitled Pro, compatible Core, channel configuration, room mappings and the provider environment before enabling synchronization. A demo website or installed module is not proof of provider API approval or connectivity.

The API importer can create reservation records with available guest, price and payment information. iCal import instead supplies source-managed inventory blocks and cannot reconstruct that complete business record. Do not use a shared source label as proof that the two records have the same fields or allowed actions.

Configure and verify deliberately

  1. Back up settings/data and test on an isolated environment with synthetic reservations and approved provider test access.
  2. Configure the existing API channel and map its room identity to the correct internal room type. Review quantity, dates, currency and any supported price/inventory mapping.
  3. Inspect the module’s job/log and reservation results independently. Verify create, modification and cancellation events under the provider’s actual protocol.
  4. Confirm website availability and stored financial/source facts after each result. Keep browser display separate from authoritative provider evidence.

Existing API behavior is not replaced by the iCal scheduler. Do not paste an API credential into an iCal URL field, reuse webhook secrets between channels or bypass provider verification.

Avoid overlapping inventory ownership

If API and iCal cover the same external reservations, decide which owns that occupancy before enabling both. Source-local identities do not guarantee cross-protocol deduplication. Inspect duplicate-looking records instead of deleting blocks or changing quantities merely to make availability look right.

Protect credentials, full URLs and raw reservation payloads. Real Booking.com/Agoda acceptance, delivery and synchronization require separate provider evidence; this guide’s source review is not certification of those live services.

See source labels and overbooking recovery.

Was this article helpful?

Your feedback helps us improve the documentation.