Required Identifiers

Several types of identifiers may be required to access either Galileo Web Services or specific host functions in the Galileo or Apollo CRS. Please note that several types of identifiers are named "profile," either colloquially or in code. This section defines the difference between these similarly named identifiers.

Required Identifiers for GWS

The following identifiers are required for access to GWS.

Account Name (User Name) and Password	Required to access Galileo Web Services sites.
Host Access Profile (HAP)	Required for Web Service access in GWS and CRS access.

Identifiers for GWS Services

The following identifiers are required for specific Web Services or specific functions within a Web Service.

Booking Profile	Used in the Reservation Builder eBL to identify the travelers in an itinerary, contact information, forms of payment, and travel preferences. Booking Profiles are used in the BookTrip and ModifyTrip methods.
PRO-Files/Client File Plus	PRO-files™ (Apollo) and Client File Plus™ (Galileo) store traveler and travel provider information.
TravelScreen Profile	Traveler profile data that is stored as part of Galileo's TravelScreen™ product, which uses personal and business travel preferences to filter a user's response options. TravelScreen works in conjunction with PRO-Files/Client Files.

Host Access Profile

A Host Access Profile (HAP) is required for access to Web Services in Galileo Web Services. The HAP is typically identified in the SOAP request for a service as a <Profile> element. HAPs should be obtained through your Galileo International representative before beginning your development process.

The HAP combines several types of identifiers into one "master" identification profile: the Pseudo City Code (PCC), Structured Data Identity, Host Sign On, Password, Host Identity, and additional identifiers for XML Select components. As such, the HAP identifies the customer to Galileo Web Services, provides permissions to specified services, and provides permissions and access to various CRS functions.

An organization typically uses more than one HAP. Users may have overlapping HAPs for various types and levels of access:

Service Bureaus should use the PCC of the agency or organization that the Service Bureau is representing.
One customer can have multiple HAPs.
Multiple users can be associated with one HAP.
Multiple HAPs can be associated with one user.
Separate HAPs are required for access to the Apollo or Galileo CRS. Each CRS maintains separate databases; identification on one CRS is not necessarily recognized on the other CRS.

Note: Most Galileo Web Services require a single HAP for access to a specific CRS. However, a single call to Flight Information eBL requires an HAP for each CRS, if full flight information data responses are desired. See How Flight Information eBL Works for more information.