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.