Booking Detail API
This method is used to query the current detail record of an existing booking.
The response keeps the existing fields unchanged. The room, meal/board, price, currency, and payment fields below are additive for existing integrations.
π Endpointβ
GET https://mg.mescogo.com/gw/api/booking/booking-detail?bookingID=1531561
| Property | Value |
|---|---|
| URI | BaseURL/api/booking/booking-detail?bookingID={bookingID} |
| Method | GET |
| Content-Type | application/json |
π Request Parametersβ
| Parameter | Type | Description |
|---|---|---|
bookingID | String | Booking identifier query parameter. Send the exact ConfirmationNumber or BookingId returned by booking, booking-detail, or booking-list. |
π Authorizationβ
This endpoint requires a Basic Authorization header, using the same API client credentials as the other booking endpoints.
π€ Example Requestβ
GET /gw/api/booking/booking-detail?bookingID=1531561 HTTP/1.1
Host: mg.mescogo.com
Authorization: Basic base64(username:password)
π₯ Response Parametersβ
| Parameter | Type | Description |
|---|---|---|
timestamp | String | Server timestamp in ISO-like string format |
content | Object | Booking detail payload |
content.status | String | Booking status |
content.dates.from | String | Stay start date |
content.dates.to | String | Stay end date |
content.bookingId | Integer | Booking identifier |
content.leadGuest | Object | Lead guest information |
content.leadGuest.guestId | Integer | Lead guest identifier |
content.leadGuest.birthDate | String | Lead guest birth date |
content.leadGuest.name.first | String | Lead guest first name |
content.leadGuest.name.last | String | Lead guest surname |
content.leadGuest.contact | Object | Lead guest contact details |
content.leadGuest.title | String | Lead guest title |
content.leadGuest.age | Integer | Lead guest age |
content.propertyId | Integer | MescoMG hotel identifier |
content.roomName | String | Room name when available in the reservation data |
content.meal | String | Meal or board name/code when available from booking detail data |
content.board | String | Board code/name when available, for example BB, HB, FB, AI, or RO |
content.price | String | Booking/order price when available |
content.currency | String | Currency for content.price |
content.isPaid | Boolean | Conservative paid flag. true only when an explicit booking detail settlement signal indicates paid/settled/captured |
content.paymentStatus | String | Booking detail payment status when available. If there is no reliable settlement signal, this is unknown and isPaid is false |
π₯ Example Responseβ
{
"content": {
"status": "confirmed",
"dates": {
"from": "2026-12-29",
"to": "2026-12-31"
},
"bookingId": 1531561,
"leadGuest": {
"guestId": 1,
"birthDate": "1989-05-11",
"name": {
"first": "John",
"last": "John"
},
"contact": {
"address": "Example Street 10",
"city": "Antalya",
"country": "TR",
"nationality": "TR",
"email": "john@example.com",
"phone": "+90 555 000 00 00",
"state": "Antalya",
"zip": "07000"
},
"title": "Mr",
"age": 36
},
"propertyId": 26090,
"roomName": "Deluxe Sea View",
"meal": "BB",
"board": "BB",
"price": "456.78",
"currency": "EUR",
"isPaid": false,
"paymentStatus": "unknown"
},
"timestamp": "2026-03-31T10:15:00.000Z"
}
β οΈ Notesβ
- The endpoint does not accept a JSON body;
bookingIDmust be sent in the query string. - If the booking is not found or the detail lookup fails, the API returns the same generic response shape with
ResultMessageset toRecord Not FoundorAn Unexpected Error Occurred. - Guest name fields are returned in the reservation data. Treat the values exactly as returned by the API.
content.statusdescribes booking status only. A confirmed booking is not treated as paid unless an explicit payment settlement signal is returned in booking detail data.