This month, we are launching exciting product updates in Lemax. Learn about the details below (available from July 10th, 2026).

Additional API Field – Internal Notes

What’s new

The REST API now exposes Internal Notes for Accommodation, Transportation, and Tours. Internal Notes is returned on both the Search and Detailed Description endpoints, at the product level and unit level. The field is returned only when the new request parameter IncludeInternalNotes=true is set, so existing integrations are not affected.

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

Clients who use the REST API as a static data export source could read Itinerary, Description, and Short Description, but not Internal Notes. The descriptive field set exposed through the API was incomplete for clients building their own itineraries and AI workflows on top of L5 data.

Benefit for the users

Clients now get the full set of descriptive fields directly from the API, including Internal Notes, for both products and units. They can pull this content as part of their normal static data export and use it for their own needs. The change is additive and opt-in, so it does not affect anyone who does not request the field.

How it works

New IncludeInternalNotes parameter

• A new boolean request parameter IncludeInternalNotes (default false), controls whether Internal Notes is returned. It applies to both Search and Detailed Description endpoints across all three product types. With the default behaviour, no Internal Notes are returned, and responses are unchanged. Invalid values are rejected using the same error pattern as other REST parameters.

Internal Notes on Detailed Description endpoints

• When IncludeInternalNotes=true is set, the Detailed Description response for Accommodation, Transportation, and Tours includes Internal Notes at the product level and unit level. HTML formatting is preserved, the same as Description and Short Description. When the Internal Notes are empty, the field is returned as empty.

Internal Notes on Search endpoints

• When IncludeInternalNotes=true is set, each result in the Search response includes Internal Notes at the product level and unit level, with HTML formatting preserved. Internal Notes is returned in the language set in the request; if no language is set, it falls back to the default language. When the Internal Notes are empty, the field is returned as empty.

Not included

• Flights endpoints, API versions older than REST, DWH/ADI changes, filtering or searching by Internal Notes content, and L5 back-office changes are out of scope for this update. Internal Notes is intended for internal use; the client is responsible for content classification in their own data.

Rent-a-car pick-up/drop-off locations not showing on correct columns in ops report

What’s new

The operations report now shows rent-a-car pick-up and drop-off locations from the reservation item in the correct columns.

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

When booking a rent-a-car, users select pick-up and drop-off destinations on the reservation item, and this information is saved on the item. However, the operations report did not reflect it correctly. The pickup location and dropoff location columns were empty for rent-a-car items. Operations teams could not see from the report where a specific vehicle needed to be picked up or returned without opening the reservation itself.

Benefit for the users

Operations teams now get accurate, booking-specific location data directly in the report. They can immediately see where each rent-a-car needs to be delivered and collected, without cross-checking individual reservations. This removes manual lookups, reduces the risk of operational errors such as sending a vehicle to the wrong location, and makes the report reliable as a single source of truth for daily rent-a-car logistics.

How it works

Pickup and dropoff location columns for rent-a-car items

The pickup and dropoff location columns, previously empty for rent-a-car, now show the destinations from the reservation item.

Rooming list enhancements

What’s new

The rooming list (and related Operations documents) can now show more data taken directly from the Regular Reservation. We extended the XML schema used by the Document Engine to expose the Regular Reservation Branch Office, Department, and Custom Fields. These fields can be added to custom rooming list templates so the document reflects the organizational and custom data held on the reservation.

Please contact support@lemax.net for additional information or advisory services on how this update could be set up for your instance, or if you have any additional inquiries..

Problem being solved

Until now, the only Branch Office data available in the rooming list XML came from the Operational Reservation. Clients who do not manage reservations through the Operations Report had no way to display Branch Office and Department data that originates from the Regular Reservation. Regular Reservation Custom Fields were also not exposed in the XML, so they could not be used in rooming list documents.

Benefit for the users

Users can now build rooming lists that include organizational and custom data coming from the Regular Reservation:

• Show the Regular Reservation Branch Office on the rooming list.
• Show the Regular Reservation Department on the rooming list.
• Use Regular Reservation Custom Fields in rooming list documents.

The change is backward compatible. Existing XML structure and integrations keep working, and default document templates are not affected unless a client explicitly configures the new fields.

How it works

Item 1 — Regular Reservation Branch Office & Department in XML

The Document Engine XML now includes the Branch Office and Department assigned to the Regular Reservation. Values are populated dynamically from the reservation, with correct mapping per reservation when multiple branch offices exist. These fields can be added to custom rooming list templates.

Item 2 — Regular Reservation Custom Fields in XML

Custom Fields defined on the Regular Reservation are now exposed in the XML output. Multiple custom fields are supported. If a field is empty or missing, XML generation does not fail — the node is simply empty or omitted. Custom field structure can differ between clients, and this is handled dynamically.