{"id":43822,"date":"2020-03-04T19:43:47","date_gmt":"2020-03-04T23:43:47","guid":{"rendered":"https:\/\/opentravel.org\/?p=43822"},"modified":"2025-08-12T05:35:55","modified_gmt":"2025-08-12T12:35:55","slug":"opentravel-messaging-business-functionality","status":"publish","type":"post","link":"https:\/\/opentravel.org\/opentravel-messaging-business-functionality\/","title":{"rendered":"OpenTravel Messaging Business Functionality"},"content":{"rendered":"\n<p>The OpenTravel specification contains the building blocks for business functionality. <\/p>\n\n\n\n<p>With interoperability at its core, the specification&#8217;s object model design spans numerous travel segments.  <\/p>\n\n\n\n<p>OpenTravel Messaging is designed to reuse elements across travel segments so that there is an easy to understand architecture that facilitates partnerships and ease of integration.<\/p>\n\n\n\n<p>In addition to established suppliers, including airline, car rental, and hotel, OpenTravel schema products support emerging segments such as day tours &amp; activities, golf, and ground transportation.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Built by the Travel Industry, For the Travel Industry<\/h3>\n\n\n\n<p>Since 2001, OpenTravel has built, promoted and evolved the data messaging standard for the travel industry. The combined efforts of all of our stakeholders over the years have resulted in a unifying specification that has been implemented by hundreds of travel companies &#8211; representing thousands of brands and properties &#8211; worldwide to create commercial solutions.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Features Enabled by OpenTravel Messaging<\/h3>\n\n\n\n<p>Millions of messages are exchanged every day using OpenTravel schema&#8230;<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"\"><tbody><tr><td> <ul>\n<li>Application Connectivity<\/li>\n<li>Booking Documents &amp; Queues Check-ins<\/li>\n<li>Customer and Partner Accounts<\/li>\n<li>Customer Profiles<\/li>\n<li>Descriptive Information<\/li>\n<li>Dining &amp; Meal Plans<\/li>\n<li>Error &amp; Warning<\/li> \n<li>Handling Fares &amp; Booking Rules<\/li>\n<li>File Attachments<\/li>\n<li>Groups &amp; RFPs<\/li>\n<li>Holds &amp; Unholds<\/li>\n<li>Inventory<\/li>\n<li>Inventory Exchanges<\/li>\n<li>Itineraries<\/li>\n<li>Locations<\/li>\n<\/ul> \n<\/td>\n<td>\n<ul> \n<li>Loyalty Programs<\/li>\n<li>Non-Inventory Items<\/li>\n<li>Notifications<\/li>\n<li>Packages<\/li>\n<li>Dynamic Packaging<\/li>\n<li>Payment &amp; Identification Verification<\/li>\n<li>Pricing, Quotes &amp; Commissions<\/li>\n<li>Rates &amp; Rate Rules<\/li>\n<li>Reservations (Bookings)<\/li>\n<li>Search &amp; Availability<\/li>\n<li>Search &amp; Display (No Availability)<\/li>\n<li>Seat Availability &amp; Information<\/li>\n<li>Shore Excursions<\/li>\n<li>Special Services<\/li>\n<li>Terminal Messaging<\/li>\n<li>Ticket Fulfillment<\/li> \n<\/ul> \n<\/td><\/tr><\/tbody><\/table><\/figure><\/li>\n","protected":false},"excerpt":{"rendered":"<p>The OpenTravel specification contains the building blocks for business functionality. With interoperability at its core, the specification&#8217;s object model design spans numerous travel segments. OpenTravel Messaging is designed to reuse &#8230;<\/p>\n","protected":false},"author":6,"featured_media":45248,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"content-type":"","wds_primary_category":0,"footnotes":""},"categories":[17],"tags":[],"class_list":["post-43822","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-specification"],"acf":[],"featured_image_src":"https:\/\/opentravel.org\/wp-content\/uploads\/2020\/03\/open-travel-object-model-577x400.jpg","featured_image_src_square":"https:\/\/opentravel.org\/wp-content\/uploads\/2020\/03\/open-travel-object-model.jpg","author_info":{"display_name":"Jeff ErnstFriedman","author_link":"https:\/\/opentravel.org\/author\/jeffe\/"},"_links":{"self":[{"href":"https:\/\/opentravel.org\/wp-json\/wp\/v2\/posts\/43822","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/opentravel.org\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/opentravel.org\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/opentravel.org\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/opentravel.org\/wp-json\/wp\/v2\/comments?post=43822"}],"version-history":[{"count":0,"href":"https:\/\/opentravel.org\/wp-json\/wp\/v2\/posts\/43822\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/opentravel.org\/wp-json\/wp\/v2\/media\/45248"}],"wp:attachment":[{"href":"https:\/\/opentravel.org\/wp-json\/wp\/v2\/media?parent=43822"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/opentravel.org\/wp-json\/wp\/v2\/categories?post=43822"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/opentravel.org\/wp-json\/wp\/v2\/tags?post=43822"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}