Beds24 enhancements

← Back to Channel sync

Beds24 connector shipped several enhancements in the June-July batch.

Reservation pull now covers Beds24-only properties

Earlier the reservation-pull path discovered properties from the Hospitable account only. Properties added to Beds24 but not Hospitable were silently invisible — reservations for them never synced.

syncReservations + fullSyncReservations discover from both connector paths. A Beds24-only property's reservations land in the platform on the same cadence as Hospitable-managed ones.

Guest names on reservation pull

Beds24 API tokens missing the read:bookings-personal scope caused reservations to arrive with empty guest names. Operator saw "Guest #6428351182" on the calendar.

Fix in

• Setup validates the Beds24 token scope at connect time; warns operator if read:bookings-personal is missing.
• Existing reservations with empty guest names retry the fetch when scope is added.

Multi-word amenity encoding

Beds24 amenity push earlier failed silently for amenity names containing spaces ("Free WiFi" → API rejected).

Rate + availability push wired

The dormant push pipeline (rate / availability / content → Beds24) went live once the beds24RoomId mapping was resolved. Now edits in V28 flow to Beds24 via the Channel sync engine.

Connector editor in V28 PM

The Beds24 / Hospitable connector editor (provider + property ID + Test Connection + Map room) ported into the V28 Properties → Configuration tab. Earlier operator bounced to legacy /admin/properties to edit the connector; V28 now handles it.

• Provider dropdown — Beds24 / Hospitable.
• Property ID — the ID on the channel side.
• Room map — map Beds24 room IDs to your properties (required for the rate/availability push in.
• Test Connection — one-tap fires a read call + shows OK / error inline.