Push ARI Signal
When the ARI changes, the notification signal of the corresponding hotel will be pushed. After receiving the signal, the distributor needs to call Price and Restrictions interface and Inventory Query interface to obtain the real-time house price according to the message content. refer to Enumeration Dictionary
Push Protocol#
https POST
Huazhu side request timeout request.timeout = 3s
Description#
- when the regular price room inventory changes, the promotion room inventory must change, so the docking party needs to pull the corresponding promotion room inventory of the hotel
- when the regular price room price changes, the promotion price must change, so the docking party needs to pull the corresponding promotion room price of the hotel
- In the early stage of GDS, there will be redundant room inventory change push situation when the regular room inventory becomes 0, so the docking party needs to pull the time rental room inventory.
Push parameters#
| Parameter | Type | Required | Maximum length | Example | Description |
|---|---|---|---|---|---|
| hotelId | String | Y | 32 | 12 * * 567 | Hotel ID |
| start | Date | Y | - | Start date, format: yyyy-MM-dd HH: mm: ss | |
| end | Date | Y | - | Start date, format: yyyy-MM-dd HH: mm: ss,The change time does not include the day of end (start is required if the start end is the same day) | |
| type | String | Y | 20 | Push data type, Enumeration Dictionary | |
| roomTypeId | String | N | 20 | Room Id | |
| activityId | String | N | 9 | Promotion ID, positive price change field is empty | |
| timestamp | Date | Y | - | Change timestamp, format: yyyy-MM-dd HH: mm: ss.fff | |
| echoToken | String | Y | 20 | UUID is used by both parties to locate the problem |
[failure retry]:
1. after the request fails for the first time, it will be retried immediately
2. if the request fails for two consecutive times, it will enter the failure message queue and delay sending
3. tasks in the failure queue will increase the call interval one by one according to the number of retries, and will not be retried after more than 10 times. The docking party should consider judging whether the current message is the latest data according to the timestamp (timestamp) to avoid historical messages overwriting the latest status.
Response parameters#
| Parameter | Type | Required | Maximum length | Example | Description |
|---|---|---|---|---|---|
| status | String | Y | 10 | 1 | Status code, 1 successful,-1 failed |
| errorcode | string | N | 50 | defined by the interfacing party | |
| errormsg | string | N | 500 | The docking party defines it by itself and needs to clearly describe the cause of the problem |