[Beta] Baggage Dimensions

Attention

Please note that this feature is in Beta and has not been officially released yet.

Enable the feature

This feature can be enabled in the API request by including:

Overview

The Baggage Dimensions feature enhances the Routehappy UTA response by providing true 3D size limits for both checked and carry-on baggage.

When enabled, the response may include a dimensions object within baggage-related content (free_bags or paid_bags) for checked and carry on baggage. This object contains structured size information including length, width, height, unit, and application.

This allows channels to present exact baggage size restrictions during shopping, making it easier for travelers to compare airline products and avoid unexpected fees at the airport.

The dimensions data is derived from Optional Services (baggage sub codes) when airlines file Commercial Names in a supported format.

Where dimensions appear

The dimensions object can be returned under the "checked_bag" or "carry_on_bag" response fields directly under:

• free_bags
• paid_bags

If present, it will be included alongside existing baggage attributes. If 3D baggage dimensions are requested and valid, then the "size" field will be empty for that bag detail.

Dimensions object structure

How dimensions are derived

The dimensions object is populated by parsing the Commercial Name filed for eligible baggage Optional Services.

Filing requirements

3D baggage data is only extracted and returned when explicitly filed in the Optional Services Record S5 Commercial Name field (bytes 88–117).

• This is a free-form text field (1 to 30 characters, spaces allowed, cannot be blank).
• Routehappy does not infer 3D dimensions from any other baggage fields.
• If the Commercial Name does not contain a recognizable 3D pattern, the API will not return a dimensions object, even if the feature flag is enabled.

Commercial Name pattern

To be processed, the Commercial Name must follow a strict pattern:

[any text] + " UPTO " + [length] + " X " + [width] + " X " + [height] + " " + [unit]

There are some spaces relaxed around X's and unit.

Example

LARGE BAG UPTO 50 X 40 X 20 CM

Key rules for parsing

• The string " UPTO " must appear exactly as shown (including spaces before and after).
• Three numeric values must be provided in this exact order:
  1. Length
  2. Width
  3. Height
• Values must be separated by " X " (uppercase X with/without spaces on both sides).
• A unit must follow the height value:
  • Supported units: CM (centimeters), IN (inches)
• Any text before "UPTO" is ignored for parsing purposes.

Valid and invalid examples

Valid (dimensions will be returned)

• CARRY ON UPTO 23 X 50 X 15 CM
• BAGGAGE UPTO 55 X 40 X 23 CM
• CARRY ON UPTO 23X50X15CM
• CARRY ON UPTO 23 X 50 X 15CM

Invalid (dimensions will NOT be returned)

• CARRY ON 23 X 50 X 15 CM (missing UPTO)
• CARRY ON UPTO 23-50-15 CM (incorrect separators)
• CARRY ON UPTO 23 X 50 CM (missing a value)
• CARRY ON UPTO 23 X 50 X 15 (missing unit)
• CARRY ON UPTOX50X15CM (no space after UPTO)

Field mapping logic

When the Commercial Name is valid:

• application → always "up to"
• length → first numeric value after UPTO
• width → second numeric value
• height → third numeric value
• unit → parsed from the unit provided (CM or IN)

If the Commercial Name does not match the required format, the dimensions object will not be included in the response.

Example response

Notes

• The dimensions object is only returned when valid dimension data is detected.
• Valid data requires both:
  • correctly formatted Commercial Name, and
  • proper Sub Code linkage via Note Text
• This feature enhances existing baggage content and does not replace any current fields.