Skip to main content

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
PropertyValue
URIBaseURL/api/booking/booking-detail?bookingID={bookingID}
MethodGET
Content-Typeapplication/json

πŸ“‹ Request Parameters​

ParameterTypeDescription
bookingIDStringBooking 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​

ParameterTypeDescription
timestampStringServer timestamp in ISO-like string format
contentObjectBooking detail payload
content.statusStringBooking status
content.dates.fromStringStay start date
content.dates.toStringStay end date
content.bookingIdIntegerBooking identifier
content.leadGuestObjectLead guest information
content.leadGuest.guestIdIntegerLead guest identifier
content.leadGuest.birthDateStringLead guest birth date
content.leadGuest.name.firstStringLead guest first name
content.leadGuest.name.lastStringLead guest surname
content.leadGuest.contactObjectLead guest contact details
content.leadGuest.titleStringLead guest title
content.leadGuest.ageIntegerLead guest age
content.propertyIdIntegerMescoMG hotel identifier
content.roomNameStringRoom name when available in the reservation data
content.mealStringMeal or board name/code when available from booking detail data
content.boardStringBoard code/name when available, for example BB, HB, FB, AI, or RO
content.priceStringBooking/order price when available
content.currencyStringCurrency for content.price
content.isPaidBooleanConservative paid flag. true only when an explicit booking detail settlement signal indicates paid/settled/captured
content.paymentStatusStringBooking 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; bookingID must 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 ResultMessage set to Record Not Found or An Unexpected Error Occurred.
  • Guest name fields are returned in the reservation data. Treat the values exactly as returned by the API.
  • content.status describes booking status only. A confirmed booking is not treated as paid unless an explicit payment settlement signal is returned in booking detail data.