This article provides a comprehensive guide to Nezasa's Juniper connector and its main use cases. Juniper is a direct accommodation integration used to search and book hotel supply in TripBuilder. This integration connects directly to the Juniper Webservice API for accommodation products, allowing you to access your contracted Juniper accommodation inventory. For a complete list of direct hotel integrations, see Supplier and Service Integrations Available in TripBuilder.

The Juniper connector supports the standard booking flow for accommodation products. The following table details the supported use cases:

To display a hotel in TripBuilder, the hotel must be present in the active data feed available through your specific Juniper connection. Seeing a hotel in Free Sale, GIATA, or another supplier system does not guarantee that it will appear through Juniper in TripBuilder. The inventory must be visible and available in the Juniper platform specifically for the credentials and distribution channel configured for your TripBuilder instance.

If you compare a single Juniper connection (such as Travco's Juniper) to other setups like Nezasa marketplace supply (which aggregates multiple bedbanks), you might notice a limited supply. This is normal and reflects the specific inventory available in your connected Juniper environment. If you are testing in a staging environment, the staging environment connects to the supplier's test systems. These test systems often have limited content and may not be entirely stable. For more details on testing, see Is there a test system / environment?.

If you find that specific hotels are not being returned in the Planner, perform the following steps:

TripBuilder places supplier hotels according to geographic coordinates provided by the supplier. If the coordinates received from Juniper are incorrect, the hotel might appear under the wrong area in the Planner. To fix coordinate errors, perform the following steps:

The Juniper integration does not use the Connect API NBC flow. Unlike other integrations that import descriptive data via an NBC endpoint, Juniper retrieves hotel content directly through the active connection. For integrations where the NBC endpoint is implemented, see Sourcing Hotel Non-Bookable Content (NBC) Independently. To learn more about standard API-based accommodation setups, see Connect API: Accommodations.

If you encounter issues with missing hotels, incorrect coordinates, or inventory not being returned in the Planner (such as in the TUI Portugal Modular Trips Planner), contact Nezasa support with the following details:

To learn more about configuring suppliers and managing credentials, see What information is needed to configure a Supplier on TripBuilder?. If your supply contract includes geography-specific rates, you can also explore Source Market in TripBuilder.