This month, we are launching exciting product updates in Lemax. Learn about the details below (available from 13th February 2025).

Passenger update on reservation insert

What’s new

A new passenger identification mechanism has been introduced to prevent duplicate passenger records when creating bookings via the L5 API. The system now checks for existing passengers using a unique key (First Name, Last Name, and Date of Birth) before inserting new records.

Unique Passenger Check check is automatically available to you once the release is launched. Please note that the usage of this update is controlled on the Lemax admin side and will not be enabled by default in your instance, but on request.

Problem being solved

Previously, each booking, coming via API, created a new passenger record, even if the same passenger had booked before. This led to duplicate records, making it difficult for travel agencies to track passenger history, apply rewards, or enforce travel restrictions. The new mechanism ensures that passengers are correctly identified and linked to their bookings, preventing unnecessary duplicate records while maintaining data integrity.

Benefit for the users

  • Ensures accurate passenger records, allowing better tracking of travel history.
  • Reduces manual work needed to clean up duplicate records.
  • Supports better application of rewards and restrictions based on travel frequency.
  • Leaves a clean passenger database.

How it works

Passenger Matching & Linking

When inserting a new booking via the L5 API, the system checks for an existing passenger using a case-insensitive unique key (First Name + Last Name + Date of Birth)

  • If a match is found, the existing passenger record is linked to the booking instead of creating a new entry.
  • If multiple matches exist, the newest passenger record is used.
  • If no match is found, a new passenger record is created.

Passenger Record Updates

Through InsertReservation API request there are 4 paramteres that are being forwarded regarding the passenger information.

  • Name
  • Surname
  • Date of Birth
  • Gender

Once that is checked and the passenger is linked to the correct existing passenger record, all other passenger data will be forwarded by using the PassengerUpdate API method.

Additional Uniqueness Check Rules

The uniqueness check is only applied if:

  • The Passenger ID from the request is linked only to the current booking and no other reservations.
  • All unique parameters (First Name, Last Name, and Date of Birth) are provided in the request.

If these conditions are not met, the uniqueness check is not applied, and the system follows standard passenger creation rules.

Extend Passenger pick-up/drop-off functionality in API

What’s new

We’ve upgraded API, GetReservation method, to retrieve Passenger transfer data when available, for PackageTransfer and Excursion service Reservation items.

This update is automatically available to you once the release is launched. Please note that the usage of this update could depend on system setups (which modules/products you use) and user roles.

Problem being solved

Passenger transfer data was previously unavailable in API, which created challenges in providing end customers with accurate and detailed transfer information through your portal.

Benefit for the users

With this update, transfer data is now seamlessly retrieved via the GetReservation API method, eliminating the need for manual intervention. This ensures that your portal can display more comprehensive and up-to-date transfer details for end customers, improving their booking experience.