Query destination

Overview

Resolve a keyword, city, or location input into G-Link destination data. This is the first call in the Lightweight Integration Flow.

When to use

  • A traveler enters a destination keyword.
  • The application needs a destination ID before hotel search.

What you get

  • Flat destination objects with destination ID, type, source, names, hotel ID, and coordinates when available.

Integration notes

The response data is an array directly. Use destinationType and source to distinguish hotel, city, district, business-area, Google, Baidu, and other results. Pass the chosen destinationId to Get hotel list.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

Pass the business request body directly. Do not wrap it in header / businessRequest.

string
required

Keyword

string

City code, using the Glink city code. If both cityCode and keyword are provided, destination information under the specified city is returned.

string

Destination type to return: 1 - hotel; 2 - city.

number

Data source: 0 - Glink; 1 - Google; 2 - Baidu.

Responses

Language
Credentials
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json