endpoint: https://travelmap.tech/map/room
\nheader:
POST - GZIP - TEXT PLAIN
access: credential / IP
\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[],"owner":"12680266","collectionId":"0a262d4b-f6b8-4a40-b30b-0d3e68d34c95","publishedId":"2sA2rGuejB","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"FF6C37"},"publishDate":"2024-04-03T15:02:48.000Z"},"item":[{"name":"All usages: static/hybrid/deferred/batch/on-the-fly/real-time","id":"0fea1f7a-9138-4d33-8c62-8c67e3092486","protocolProfileBehavior":{"disableBodyPruning":true,"disabledSystemHeaders":{"content-type":true}},"request":{"method":"POST","header":[{"key":"content-type","value":"text/plain"}],"body":{"mode":"raw","raw":"{\r\n \"credential\": \"mycredential\",\r\n \"list\": [\r\n {\r\n \"hid\": 79683,\r\n \"supplier\": \"expedia\",\r\n \"rcode1\": 156641,\r\n \"rcode2\": \"ex1\",\r\n \"amount\": \"ex2\",\r\n \"name\": \"twin or double \"\r\n }\r\n ]\r\n}","options":{"raw":{"language":"text"}}},"url":"https://travelmap.tech/map/room","description":"Add to the list array the rooms you have.
\nIt can be:
\n1 supplier - 1 hotel - 1 room.
\nmultiple suppliers - 1 hotel - 1 room.
\n1 supplier - 1 hotel - multiple rooms.
\n1 supplier - multiple hotels - multiple rooms.
\nmultiple suppliers - 1 hotel - multiple rooms.
\nmultiple suppliers - multiple hotels - multiple rooms.
\n...
\nThe API returns them sorted by given supplier alias and hotel code.
\nMaximum accepted: 30k rooms.
\nBest practice: Send a rooms list per hotel.
\nMap the room name & it's description.
\nWhen passing both, the A.I. retains what is in the name & complement it with what is found in the description.
\nHow to double-check on room name vs API:
\nIf the supplier's field returns cancelable: true but the room name says none cancelable, you can automatically step aside rooms with policy issues driving to a customer problem. You confront them & if different, you can step aside the room for requalification. Valid for any topic.
\nOverride a board-meal, policy and bed type:
\nyou can replace board-meals & policies & bed types by using the ones returned by the supplier's API.
\nDoing so you remove the one present in the name by the one you decide. This allows to normalize the mapping based on the supplier's returned one.
\nFor it, add **** (4 stars, multipliers) at the start of description. see below.
\nComplement your mapping with the description:
\nIf **** is not present at the description's start, the mapper will prioritize what is in the name & complement the mapping with what is in the description. Matching, ranging & scoring are based only on the name.
\nNote the HTML inside the description. You can pass html either in the name or the description.
\nThe HTML must not be too complex. The one returned by expedia is ideal.
\nThe description has to stay \"simple\" & should not be too long or too complex or too messy like an html div or with data not related to the room.
\n{\n \"credential\": \"mycredential\",\n \"list\": [\n {\n \"hid\": \"123456\",\n \"suppl\": \"supplier\",\n \"rcode1\": \"7654321\",\n \"rcode2\": \"booking ref: 234567\",\n \"name\": \" 2 bdrm duplex Luxussuite with an amazing ocean view on corner.\",\n \"description\": \"<div class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml' class='preserveHtml'>room only</b> - 2 king and murphy bed 
 1 shared bathroom- free parking - ADA compliant hearing impaired (3ad+2ch) breakfast for 2 no cancel</div>\",\n \"amount\": 1200\n }\n ]\n}\n\nNote the **** at the start of description. you can chain (space separated) board-meals & policies.
\nIn the below example, we are asking the mapper to discard the board-meal & policy in the name and replace them by the ones from description.
\n{\n \"credential\": \"mycredential\",\n \"list\": [\n {\n \"hid\": \"123456\",\n \"suppl\": \"supplier\",\n \"rcode1\": \"7654321\",\n \"rcode2\": \"booking ref: 234567\",\n \"name\": \" 2 bdrm duplex Luxussuite CANCELABLE full board.\",\n \"description\": \"**** none cancelable halfboard\",\n \"amount\": 1200\n }\n ]\n}\n\nex: 4 different suppliers. same hotel. 1 room.
\n{\n \"credential\": \"mycredential\",\n \"list\": [\n {\n \"hid\": \"1234567\",\n \"suppl\": \"bedbank1\",\n \"rcode1\": \"7654321\",\n \"rcode2\": \"this is a wildcard\",\n \"name\": \"hilton 2 bdrm large duplex Luxussuite with an amazing sea view on corner. kitchen and balkon - private pool & Jacuzzi on rooftop- room only - 2 king and murphy bed - free parking - ADA compliant (3ad+2ch) breakfast for 2 no cancel\",\n \"amount\":\"1234.54\"\n },\n {\n \"hid\": \"AA2345\",\n \"suppl\": \"bedbank2\",\n \"rcode1\": \"7654321\",\n \"rcode2\": \"booking ref: 234567\",\n \"name\": \" 2 bedrooms wide duplex suite deluxe corner sea view balcony - private pool 2 king and extra bed\",\n \"amount\":\"1200\"\n },\n {\n \"hid\": \"AA2123\",\n \"suppl\": \"gds1\",\n \"rcode1\": \"AAD435444\",\n \"rcode2\": \"//ERTYYO 6543222 REZZ67899@@<mention value=\"3\">3</mention>##\",\n \"name\": \" 2 bedrooms wide duplex suite deluxe corner sea view view balcony\",\n \"amount\":\"1310\"\n },\n {\n \"hid\": \"76589054\",\n \"suppl\": \"gds2\",\n \"rcode1\": \"TT5555\",\n \"rcode2\": \"this is a wildcard\",\n \"name\": \" 2 bdrm large dupleix suite delujo corner vista mar balcon\",\n \"amount\":\"1299\"\n }\n ]\n}\n\nOPTIONAL: supplier, hid, rcode1, rcode2 & amount are optional. If omitted, \"unset\" is set as hotel-code default & rcode1 is the room's index position in the list.
\nBest practice is to leave the mapper do the sorting on supplier's name & hotel code.
\nThe mapper is data agnostic, use an alias for the supplier's name if you prefer.
\nIf you want to benefit the finTech & optimized price finder, you need to pass a base rate (amount) common across suppliers. Your pick. It can a net or vat incl...
\nNOTE: rcode2, acting as a wildcard, accepts a long text string or stringified json.
\nNOTE 2: The mapper is database-less and doesnt records any of your data.
\n4 correlative unique mapping tools
4 complementary angles of view
4 reciprocal ML dataset classifications
The response is a hierarchized indexed JSON.
\nUse the indexes for your application. For instance, the group & range indexes are ideal for elastic search and database indexing, autocomplete search on your UX. Being normalized, the database indexes table size stays light with optimized performance & precision.
\nLists mapped rooms with the complete separation.
Includes the translations, rewritten descriptions in 5 languages.
Customizable.
\nIndexing: supplier -> hotel code ->mapped rooms
\nNOTE: some amenities dictionaries like SHR (shared) or BLC (balcony/terrace) are separated from the AMN (amenities) list. Those Amenities are important for matching rooms and therefore in a specific dictionary.
\nmapid: It lists the room's attributes codes. It can be reverse engineered using the dedicated API call. Based on those codes, the API rebuilds the room's like if mapping its name.
\nHow to filter the best deals:
\nif a room returns groupCheapest true, the room is the cheapest for price optimization.
\nil a room returns rangeCheapest true, the room is the cheapest within its market positioning.
\nil a room returns both true, the room is the allover best deal across suppliers.
\nFor it to work, you need to pass a base rate common across suppliers (amount). a net rate or vat incl...
\nIndexed by supplier -> hotel-code -> room
\nLists matched groups where similar rooms fall.
Grouping similar rooms together for price optimization.
Customizable.
\nMatching is a shortcut to directly access room-codes.
\nLists matched groups where similar rooms fall. Similar rooms are grouped together into type groups (customizable).
\nYou can find each room group in the mapping object, property \"group\".
\nGroup also act as an index for databases & text search indexing. (elastic, mysql...). Being normalized & unified, it reduces the size and optimizes requests execution time. (autocomplete)
\nHow to deal with duplicates:
\nWhen talking about removing duplicates, you dont actualy \"remove\" them but group all similar rooms (either in one or across multiple suppliers) into a common group. You then sort by rates to get the cheapest to filter & step aside the others.
\nIn the case you are doing a duplicates removal on a static file, the logic stays the same. Pick the preffered one in the group.
\nNOTE: Matching is a shortcut to quickly sort room codes for similar rooms across suppliers, by room types (organized as group indexes).
\nIndexing: group name -> supplier -> hotel code ->room codes
\nLists rooms by quality & range. A new unique market angle of view.
A range group is defined with 3 classifications in mind: moderate/std, luxe & high-end.
Customizable.
\nRanging is a shortcut to directly access room-codes based on range.
\nThe intel defines a range group for the room, with 3 classifications in mind: moderate/std, luxe & high-end.
\nNOTE: Ranging hierarchies hotels or a market at a higher sentimental level, for a unique vision & analytic.
\nIndexing: range -> group -> supplier -> hotel code ->room codes
\nLists rooms grouped by attribute weight.
What room type ? A view ? a balcony ? an amenity ? they each add weight (value) to the room. Higher the weight, higher the room intrinsic value. All topics taken into account.
Customizable.
\nScoring is a shortcut to directly access room-codes based on attributes score.
\nNOTE: Scoring hierarchies hotels' rooms or a market, from low end to high end, like you would do with a slider from low to high. More offered by the room, higher the score.
\nIndexing: score -> group -> supplier -> hotel code ->room codes
\nIMPORTANT NOTE: Matching, ranging & scoring are shortcuts to directly access the room-codes on indexes. You can reproduce it or even aggregate your own market hierarchy by merging group, range & score properties while iterating the rooms listed in \"mapping\" main response property.
\nTopic/Dictionaries 3 letter codes properties in response:
\nAvailable as direct shortcuts at the object root (comma separated) or inside the dataset for details.
\nThe dataset property returns the detailed separation & labeling per topic, per element.
\nEach topic element has its own classification.
\nFor instance:
\nTYP & CAT classification is aimed at the room range (moderate, luxe, high-end).
\nAMN (amenities) classification is aimed at usage like outdoors, comfort, winter sports...
\nYou can use the classification to have the amenities sorted by category in your UX & database.
\nA sentimental classification is also returned when appropriate, & ranges from \"atypic\" to \"moody\" or \"stylish\" & much more...
\nIMPORTANT NOTE: In addition to implementing a highly qualified rooms inventory, using the mapping, group, range & score dataset allows to directly upload it inside openAI for instance. Your conversational chatBot knows the hotel code & room code he is talking about. More importantly, the dataset is the same for your room inventory AND to upload to chatGpt (langChain, RAG model). Both are identical & syncronized in your booking flow. contact me to know more.
\nSeparation, group, range, score & lang are customizable to your needs.
\nSeparation within each topic dictionary is coma separated. (easy UX & dropdowns)
\nDescription rewrite is configurable. ( 2 bedrooms suite....Suite 2 bedrooms....)
\nMatching. You set what topic dictionaries to use to define a similar group. Group is the canonical aggregation of a preset number of topics/dictionaries you can define. (default preset)
\nRanging. You define your own range definition, terms. (default preset)
\nScoring. You define the importance in term of value (weight) of the attributes.(default preset)
\nThe A.I. returns what he does not know or if having a doubt. Find it in the room element leftover property or get the list with the debugging main response properties.
\nThe leftovers are recorded and implemented in the NLP along the way or on demand.
\nYou can also use the API NLP call to directly add it yourself.
\nmapped object response fields:\n{\n \"hid\": {\n \"property\": \"hid\",\n \"dscrpt\": \"hotel code / id / reference / unref as default.\"\n },\n \"suppl\": {\n \"property\": \"suppl\",\n \"dscrpt\": \"supplier code / id / reference. string, integer. unref as default.\"\n },\n \"name\": {\n \"property\": \"name\",\n \"dscrpt\": \"The original concatenated string you sent.\"\n },\n \"rcode1\": {\n \"property\": \"rcode1\",\n \"dscrpt\": \"room code / id / reference.\"\n },\n \"rcode2\": {\n \"property\": \"rcode2\",\n \"dscrpt\": \"room code / id / reference / Wildcard: can a long string, booking reference.\"\n },\n \"group\": {\n \"property\": \"group\",\n \"dscrpt\": \"data orientied group for price optim at hotel level.\"\n },\n \"range\": {\n \"property\": \"range\",\n \"dscrpt\": \"The room range for analytic & superior meaning labeling.\"\n },\n \"score\": {\n \"property\": \"score\",\n \"dscrpt\": \"The room value as a number being the topic/attributes scoring total.\"\n },\n \"dataset\": {\n \"property\": \"dataset\",\n \"dscrpt\": \"The detailed separation to use for chatbt, ML & LLM\"\n },\n \"BDR\": {\n \"property\": \"BDR\",\n \"short\": \"bedroom\",\n \"dscrpt\": \"the number of bedroom.\"\n },\n \"TYP\": {\n \"property\": \"TYP\",\n \"short\": \"room type\",\n \"dscrpt\": \"the room type found (suite...)\"\n },\n \"MKG\": {\n \"property\": \"MKG\",\n \"short\": \"room marketing & name\",\n \"dscrpt\": \"the room name, superlatives.\"\n },\n \"CAT\": {\n \"property\": \"CAT\",\n \"short\": \"room category\",\n \"dscrpt\": \"the room category found (deluxe...)\"\n },\n \"VEW\": {\n \"property\": \"VEW\",\n \"short\": \"views\",\n \"dscrpt\": \"any related to views, POI, sightseeing, situation from the room.\"\n },\n \"BLC\": {\n \"property\": \"BLC\",\n \"short\": \"balcony/Patio\",\n \"dscrpt\": \"balcony, patio, terrasse...\"\n },\n \"CAP\": {\n \"property\": \"CAP\",\n \"short\": \"capacity\",\n \"dscrpt\": \"double , triple...\"\n },\n \"BED\": {\n \"property\": \"BED\",\n \"short\": \"bed type\",\n \"dscrpt\": \"king, twin...\"\n },\n \"ADA\": {\n \"property\": \"ADA\",\n \"short\": \"accessible\",\n \"dscrpt\": \"is the room accessible, roll-in...\"\n },\n \"SHR\": {\n \"property\": \"SHR\",\n \"short\": \"shared Amenities\",\n \"dscrpt\": \"anything that is shared, beds, bath...\"\n },\n \"SMK\": {\n \"property\": \"SMK\",\n \"short\": \"smoking\",\n \"dscrpt\": \"smoking or not...\"\n },\n \"AMN\": {\n \"property\": \"AMN\",\n \"short\": \"amenities\",\n \"dscrpt\": \"all known amenities found...\"\n },\n \"CAN\": {\n \"property\": \"CAN\",\n \"short\": \"cancelable\",\n \"dscrpt\": \"is the room cancelable.\"\n },\n \"REF\": {\n \"property\": \"REF\",\n \"short\": \"refundable\",\n \"dscrpt\": \"is the room refundable. \"\n },\n \"BRD\": {\n \"property\": \"BRD\",\n \"short\": \"boardMeal\",\n \"dscrpt\": \"board type.\"\n },\n \"SGL\": {\n \"property\": \"SGL\",\n \"short\": \"single Use\",\n \"dscrpt\": \"is the room single use.\"\n },\n \"PAX\": {\n \"property\": \"PAX\",\n \"short\": \"paxes\",\n \"dscrpt\": \"how many paxes, adults, childs.\"\n },\n \"FLR\": {\n \"property\": \"FLR\",\n \"short\": \"floor\",\n \"dscrpt\": \"floor level, ground, 5th, high....\"\n },\n \"PLA\": {\n \"property\": \"PLA\",\n \"short\": \"promo & Plans\",\n \"dscrpt\": \"promotions and plans.\"\n },\n \"CHA\": {\n \"property\": \"CHA\",\n \"short\": \"chain\",\n \"dscrpt\": \"hotel chain.\"\n },\n \"redFlag\": {\n \"property\": \"redFlag\",\n \"dscrpt\": \"is the room with an issue ( no window, basement, shared, inner side...).\"\n },\n \"langOut\": {\n \"property\": \"langOut\",\n \"dscrpt\": \"the translated separation sorted by term, per topic\"\n },\n \"langEN\": {\n \"property\": \"langEN\",\n \"dscrpt\": \"rewwritten description in English (customizable)\"\n },\n \"LangES\": {\n \"property\": \"LangES\",\n \"dscrpt\": \"rewwritten description in Spanish (customizable)\"\n },\n \"LangPT\": {\n \"property\": \"LangPT\",\n \"dscrpt\": \"rewwritten description in Portuguese (customizable)\"\n },\n \"LangFR\": {\n \"property\": \"LangFR\",\n \"dscrpt\": \"rewwritten description in French (customizable)\"\n },\n \"LangIT\": {\n \"property\": \"LangIT\",\n \"dscrpt\": \"rewwritten description in Italian (customizable)\"\n },\n \"LangDE\": {\n \"property\": \"LangDE\",\n \"dscrpt\": \"rewwritten description in German (customizable)\"\n },\n \"LangCN\": {\n \"property\": \"LangCN\",\n \"dscrpt\": \"rewwritten description in Chinese (in dev)\"\n },\n \"LangIN\": {\n \"property\": \"LangIN\",\n \"dscrpt\": \"rewwritten description in Hindi (in dev)\"\n },\n \"LangAE\": {\n \"property\": \"LangAE\",\n \"dscrpt\": \"rewwritten description in Hindi (in dev)\"\n }\n}\n\n