Plug-ins

Note: Add the SmartPointplug-in class attribute to define the developer and GUID (globally unique identifier). The GUID is essential if you plan on distributing your plug-in through Marketplace, as it will be used as the license. The GUID displayed on the classifications page is the value that should be used. If you are building a plug-in for use within your agency or do not plan on distributing your plug-in through Marketplace, we recommend creating a GUID through Microsoft Visual Studio (Tools > Create GUID option in the menu) and embedding the GUID in your code now. We will be adding functionality within Marketplace in early 2016 and will be asking you to ‘register’ your plug-in(s) with Marketplace by entering a few pieces of information. Once we turn on our validation, any plug-in that is not recognized by Smartpoint (via the integration with Smartpoint) will not load. For a code snippet, refer to Sample Plug-in step 3.

A plug-in is a single unit of functionality in Smartpoint. For example, the Air Availability is processed by a plug-in, and the Air sell is processed by another plug-in. Smartpoint contains a list of plug-ins that are responsible for converting a host response into an interactive response.

Types of plug-in developers

Plug-ins may be built by Travelport, agency, or third-party developers. All developers must have a Travelport Developer Portal agreement.

Travelport-developed and third-party plug-ins can be offered through the Travelport Marketplace. Agency plug-ins are deployed in a different manner (e.g., setup.exe available on an internal server or a disk). Both types of plug-ins require a key, which is required to sign the plug-in.

  • Marketplace plug-ins must be approved before they are assigned a key. The signed plug-in is then loaded to Marketplace for download or purchase.
  • Agency plug-ins do not require approval.

Developers can view a list of plug-ins being used by Smartpoint by typing the command #LISTplug-inS into Smartpoint.

Key features

  • Both DLLs and EXEs can be plug-ins.

  • Written in .NET Framework 4.
    Note: With the release of Travelport Smartpoint 7.5 the target framework changed from .net 4.0 to .net 4.6.2.

  • Plug-ins are loaded when the Smartpoint application starts. Galileo Desktop must be restarted for changes to take effect.
  • Plug-ins can be used to extend functionality with/without user interface impact.
  • Any plug-in has full access to the Smartpoint API.