Plexe / Autosuggest API v1 Status Get a free key

Hotel and destination autocomplete for travel sites

One API call turns what a traveller has typed into ranked cities, areas, landmarks, airports and hotels, with the search area and supplier ids your booking flow needs.

224 countries<50 ms median server timefree to start
  • Results appear as you type.
GET /api/suggest

What it handles

Built for the search box of a hotel booking flow, where people type half a word, misspell it, or mean an area rather than a city.

Partial and misspelled input

Prefixes match from the first letter, typos are tolerated from four characters, and any script works.

barcelna → Barcelona · 東京 → Tokyo · ao na → Ao Nang

Every kind of place

Cities, neighbourhoods, landmarks, airports by name or code, islands, regions and metro areas, each with the number of hotels it lists.

dxb → Dubai International · orlando → Orlando, Orlando (and vicinity)

Hotels and brands

Hotels appear from three characters. A brand lists its hotels; a famous hotel comes before the place it is named after.

four seasons → Four Seasons hotels · burj al arab → the hotel

The area to search

Every place has a search area: a circle for a city, a polygon or multipolygon for islands and island nations, also in ZentrumHub's own format.

maldives → its islands, not a circle round its centre

Hotel lists per place

Pick a place and page through exactly the hotels it counts, most popular first, 250 at a time, ready for an availability call.

GET /api/regions/{id}/hotels

Your ids and supplier ids

Hotels carry Vervotech, ZentrumHub, Hotelbeds and Xeni ids for approved accounts. Once we map your inventory, results return your own hotel ids too.

supplier_ids · customer_hotel_id

One request

Call it on each keystroke, debounced, with your key in a header. Responses are typed in the OpenAPI spec.

Request
curl "https://suggest.plexe.ai/api/suggest?q=ao%20na&limit=3" \
  -H "X-API-Key: $PLEXE_KEY"
Responseabridged

  "results"
    "id" "gn:1158377" "type" "city"
    "name" "Ao Nang" "label" "Ao Nang, Krabi, Thailand"
    "hotel_count" 589 "search_type" "Polygon"
  

Pricing

Per request, no contract. Start free; upgrade in the console when you need more.

Trial
Free
  • 5,000 requests a day
  • 5 requests a second per key
  • every endpoint, no card
Growth
$99 a month
  • 500,000 requests included
  • then $0.25 per 1,000
  • 50 requests a second per key, no daily cap
Scale
$499 a month
  • 5,000,000 requests included
  • then $0.10 per 1,000
  • 200 requests a second per key, no daily cap

Questions

How is this different from a general places API?

It is built for hotel search: it knows which hotels sit in each place, ranks places by the hotels people book there, returns the area to search a supplier with, and carries supplier ids. It is priced per request from free. Compared with Google Places Autocomplete.

Do I need a contract?

No. Sign up in the console and a key works straight away on the free Trial plan. Paid plans are monthly through Stripe and can be cancelled at any time.

Is it fast enough to call on every keystroke?

Median server time is under 50 ms. Debounce input by 100 to 150 ms and request up to 8 results.

Can results show only the hotels we sell?

Yes. We map your hotel list to ours; your keys can then return only your hotels, with place counts that match, and each hotel carries your own id.

Where does the data come from?

Places come from GeoNames, OurAirports and Wikidata, island outlines from OpenStreetMap, and hotels from supplier catalogues. The index is rebuilt and checked against a fixed query set before each release.