...
If a vendor submits a new user, it will only be proposed to the property. The property then must either connect the user to an already existing user within hotelkit, create a new user (and attach some access) or ignore the user in hotelkit. If the property decides to make the user available in hotelkit the user is available at GET /users. Until then the user is available at GET /users/byStatus/pendingNew. In both cases the user’s attributes can be updated via PUT /users/ID. If the property decides to ignore the user, its data can only be seen at GET /users/byStatus/ignored to prevent a new proposal by the partner.
Process
User Synchronization
The goal of the user synchronization process is that all users of the partner are available for the property within hotelkit. It should be done daily to ensure that users are synchronized regularly. The daily process is displayed in the graphic.
...