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:
...
Let’s say refresh is scheduled after every 2 hrs starting from 12:00 p.m....The changes are finished around 11:55 a.m....This would mean it will be picked up immediately in the cycle of 12 noon...The refresh process takes approx. 30 min but can take longer depending on how many changes are to be synched. Let’s assume it takes another 10 mins extra. So, by 12:40 the refresh process is completed, and you have the changes reflected just within 40 mins.
...
All the above is true only if the refresh process goes smoothly...In case if there are interruptions due to unseen circumstances like DB stability issues etc and process gets dropped then the process is not started again but will just get re-executed as per the next schedule.In such cases the delay can be even be upto 4hrs or more. But such cases are rare to occur.
...
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.
...