Skip to main content

MescoMg Hotel API

πŸ“‹ Change Log​

DateChanged ByAPIDescription
28 August 2026-Search APIClarified nationality codes, CustomRow usage, hotel-local cancellation penalty times, and USD pricing.
27 August 2026-All public APIsUpdated the customer-facing API contract and examples, added security guidance, and documented live/test base URLs.
18 May 2026-Booking List, Search, Booking, Static DataPublic API documentation update
15 May 2025--Base API

πŸ”— API Base URLs​

EnvironmentBase URL
Livehttps://mg.mescogo.com/gw
Testhttps://mgtest.mescogo.net/gw

All prices returned by the API are in USD. Cancellation penalty times are based on the hotel's local time and are returned without conversion to UTC or the customer's local timezone.

Use {BaseURL} in the endpoint examples below. Replace it with the base URL for the environment you are using; do not append /gw again.

πŸ“ API Endpoints​

APIEndpoint
Search{BaseURL}/api/price/mg-hotel-prices
Book{BaseURL}/api/booking/book
Booking Detail{BaseURL}/api/booking/booking-detail
Booking List{BaseURL}/api/booking/book-list
Booking Cancel{BaseURL}/api/booking/cancel
Service Status{BaseURL}/api/service/Status
Country List{BaseURL}/common/common/country-list
Region List{BaseURL}/common/common/region-list
City List{BaseURL}/common/common/city-list
Meal Types{BaseURL}/common/hotel/meal-types
Hotel Code List{BaseURL}/common/hotel/hotel-code-list
Hotel Detail{BaseURL}/common/hotel/hotel-detail

πŸ“Š Response status handling​

The HTTP status and the status code inside a JSON response are separate values:

LayerMeaning
HTTP 200The request reached the API. The JSON body can still contain a business or validation result in Status.Code or StatusCode.
HTTP 400The request format or model validation failed.
HTTP 401The Authorization header is missing, malformed, or not accepted.
HTTP 404The requested resource or API credentials were not found.
HTTP 409The request conflicts with the current availability or booking state.
HTTP 500An unexpected server-side error occurred.

For search and booking operations, handle the JSON body as well as the HTTP status. Common body status codes are 200 (successful), 201 (no availability), 404 (record or validation result not found), 409 (availability or booking conflict), and 500 (processing error). The exact response shape is documented on each endpoint page.