From HTNG Connectivity Wiki

Jump to: navigation, search



This version of the Guest profile is based on the data sent in the OTA_HotelAvailRQ message and is not based on the HTNG_ProfileReadRQ message.


GET guestID
returns the guest profile based on the provided guestID


Detailed name information for the customer. Follows Person Name utility object schema.
Document information for verification purposes and also used for additional filtering for common names.
Information on a telephone number for the customer. Follows Telephone utility object schema.
Information on an email address for the customer. Follows Email utility object schema.
Detailed information on an address for the customer. Follows Address utility object schema.
Information on a URL for the customer.
Name of the (self-professed) country that is claimed for citizenship using ISO 3166-1 alpha-2 value.

Things to Consider

Social Handles
Information on social profiles for the customer (LinkedIn, Twitter, Facebook, etc). May be broken down into utility which captures specific identifiers and components of the profile. (ID, @mention, URI, etc).
URL Types
Should we consider extracting URL to a utility object that captures more detail around the context of the URL.



The specification that would be replicated in a JSON format would be: HTNG Customer Profile 2014B Specification -

The message in the spec is:

HTNG_ReadRQ / ReadRequests / ProfileReadRequest

with alot of data points beneath it - such as: Customer Name, location details, type, etc Which I would see turning into a rest endpoint by guest profile ID or some other unique identifier.

FWIW - here is an example of how RoomKey serves up this data from their API: (it can be sent as XML or JSON)

Personal tools
administrative tools