Introduction: This document aims to address the most commonly asked questions about our APIs, providing clarity and guidance for a seamless integration experience.
...
1)How to create a new Rest API user?
Prerequisite:
DC should be created in MXTS.
RC should be linked to the DC created above.
...
2)What is the reservation creation flow using API inline with MXTS?
Prerequisite:
DC and RC to be used for creating the booking.
Expected stay period (arrival date, duration).
Basic required configurations like applicable rates, rentability and other such conditions that are needed for the accommodation to be bookable.
Solution: Please follow the steps mentioned below:
...
Amenities are displayed on the website and included in the API response only when the toggle shown on the screen below is enabled in MXTS.
...
Note: only the amenities of type “SIMPLE” are indexed. The other Amenity types like NUMBER and TEXT and not present in the index.
14) Why is accommodationtype/unit shown not applicable for a amenity even when the amenity is linked to accommodationtype/unit?
...
There can be multiple or one of the below mentioned reasons:
a) check whether DC is marked as "has its own representation set" in Newyse. If it is marked as true, it is available in the index; if marked as false, then it is not available in the index.b) Price cache is built only for specific DC’s and not for all. In such a case the DC of the existing price cache and the new DC should be selected in the same representation of the resource. Also, there should be rates available for the rate type of existing DC. The same rates will be followed for new DC.
b) check whether DC is marked as "has its own representation set" in Newyse. If it is marked as true, it is available in the index; if marked as false, then it is not available in the index.
Note: The 'Has Own Representation Set' toggle will soon be removed, and the 'Enabled' setting will be applied across all DCs.
16)Why are rates for some addons not calculated on the landing page of website?
We have two types of scripts that are used to populate and calculate prices in index for addons. The first one is a normal addon script (free)and is by default enabled for every concern. This script calculates the prices for all addons except the subject based addons. The second one is the ‘Additional cost script’ which is enabled only on the request of the client (chargablechargeable).This script calculates the prices for all addons including the subject based addons.
Subject based addons : The addons having rates based on subjects OR/AND having subjects selected while linking them to accommodation are referred as subject based addons.
17)How does the event generation for the event table work?
Please refer the following flow chart to understand the event generation logic in the event table.
...