Occupations (push)
Synchronization of changed reservations on the hotel side. Usage:
- Partner changes Slevomat reservation in their system and this endpoint is called to update the reservation in Termino/Slevomat
- Data with reservations that were not originated from Termino/Slevomat are ignored
Updates of occupations in multiple hotels has to be sent in multiple requests.
Request body
Response
Successful response
Example response
{
"success": true
}Changes
Changed in 2 of the 10 revisions of this API.217
- ▲
added the new required request property
occupations/items/roomTypeIdnew-required-request-property
- ○
api tag
Termino endpointsaddedapi-tag-added
- ○
api tag
Push endpointsremovedapi-tag-removed
- ○
the request property
occupations/items/roomIdbecame optionalrequest-property-became-optional
- ○
request property
occupations/items/roomIddeprecatedrequest-property-deprecated
- ▲
- ▲
the request property
occupations/items/roomIdbecame requiredrequest-property-became-required
- ●
removed the request property
occupations/items/roomTypeIdrequest-property-removed
- ○
api tag
Push endpointsaddedapi-tag-added
- ○
api tag
Termino endpointsremovedapi-tag-removed
- ○
request property
occupations/items/roomIdreactivatedrequest-property-reactivated
This revision also has 10 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲