...
| Code Block |
|---|
{
"api_version": "2",
"status": "Success",
"requests": {
"id": 308,
"room": "32",
"details": null,
"property_id": 2,
"status_id": 1,
"created_at": "2019-01-14 23:26:21",
"updated_at": "2019-01-14 23:26:21",
"category_id": 21,
"completed_at": null,
"first_time": 1,
"staff_id": null,
"guest_id": 13,
"booking_id": "1332025-4X",
"message_channel": "BookingCenter",
"message_thread": "597470647",
"assigned": null,
"status": {
"id": 1,
"name": "New",
"created_at": "2014-11-14 02:23:46",
"updated_at": "2014-11-14 02:23:46"
},
"guest": {
"id": 13,
"name": "Joe Banks",
"email": "jchieppa@gmail.com",
"phone": "7075551414",
"rewards_number": "0",
"created_at": "2018-02-07 10:49:28",
"updated_at": "2019-01-11 22:09:36"
},
"staff": null,
"category": {
"id": 21,
"name": "Self Checkin",
"department_id": 7,
"created_at": "2019-01-14 22:21:55",
"updated_at": "2019-01-14 22:21:55",
"identifier": "21"
}
}
} |
MyGuest Message Queue
While the Api endpoints can be called directly (and may eventually be by third party developers) we will be utilizing a queue to process actions and keep a history.
MG_MESSAGES Table Schema
MG_PKEY is a sequence MG_PKEY_SEQ
...
Name
...
Status Codes
...
Create or Update (if multiple 'edits' occur, the Request might already exist)
MyBookings has no role in this step.
...
Guest Details: "Self Checkin Guest Details Updated"
Payment Details: "Self Checkin Booking Edited (CC Info)"
...
e-Sign Letter Generated
...
Create or Update
...
MyGuest / BookDB Request to Booking Mapping Table
Table Schema
| Name | Nullable | Type |
|---|---|---|
| MGBK_PKEY | NOT NULL | NUMBER(22) Primary Key |
| MGBK_REQ_ID | NOT NULL | NUMBER |
| MGBK_SIT_FKEY | NOT NULL | VARCHAR2(10) Foreign Key |
| MGBK_BK_FKEY | NOT NULL | VARCHAR2(30) Foreign key |