Back to the developer overview

Data & responsibility

The right data
in the right place.

Occupancy, bookings and personal data serve different purposes. Clear separation makes your integration easier to understand and maintain.

A practical example

An occupancy calendar needs dates and status. Names, contact information and other booking details are not automatically necessary.

Occupancy is not the same as booking details

The REST API occupancy feed includes occupancies and bookings not yet converted into occupancies. For foreign or unattributed origins, it limits data to property, arrival, departure and status. Design your interface to work without protected details.

Clarify ownership first

Our recommendation: define which system owns property data, prices and availability. Document how changes are applied and how conflicts are detected. This prevents inconsistent edits across systems.

Store only the data you need

Keep only the data your workflow actually needs. Separate customer access, restrict internal visibility and plan removal of data no longer needed. Available data depends on authorisation and origin, not just on the selected endpoint.

Frequently asked questions

Why are booking details missing from some occupancies?

The occupancy feed limits data from foreign or unattributed origins to property, arrival, departure and status. This lets you display occupancy without receiving protected booking details.

Do I need guest contact details for an occupancy calendar?

Displaying occupied periods generally only requires property, dates and status. Store additional personal data only when your specific workflow needs it and access is authorised.

How do I avoid conflicting data across systems?

Define an owning system for each data type, such as property data, prices and availability. Document the transfer direction and conflict handling before the same data is edited in multiple places.