Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

File Structure

The name of the generated JSON file has the prefix PNRS_ and the timestamp in UTC, following the pattern PNRS_YYYYMMDDTHHMMSSFFFZ.json. For example, PNRS_20230512T105030923Z.json.

...

Code Block
{
  “event_details”: {...},
  "pnr_list": [
                {     
                  "record_locator_version_information": {},
                  "record_locator_information": {},
                  "passengers_information": {},
                  "flights_segment_information": {},
                  "flights_origin_destination_information": {},
                  "contacts_list": [],
                  ...
                },
                {...}
              ]
}

...

Structure of event_details

The event_details object has the following structure:

Key

Tipo Dato

Valores posibles

Descripción

Ejemplo

ObservacionesType Data

Possibles values

Description

Example

Observations

system_from

string(2:3)

C1 or airline operator code, depending on whether it is a PSS terminal or Kiu GDS terminal

Z8

company

string(4)

Unique code of the company, airline, or agency within Kiu

00Z8

channel

string

HOST, GDS

HOST

subchannel

string

In the case of GDS, it is the GDS code (C1, 1A, etc.). In the case of HOST, it is the value configured in the office table, command DNO / BI STAT.SUB-CHANNEL.

SALES OFFICE

device

string(0:10)

Kiu device that generated the transaction

LPB00Z8205

agent

string(0:9)

Kiu device that generated the transaction

HDQ00Z8SM

pnr_action

string

CREATE, MODIFY, SPLIT, DELETE

Identifies whether the event is a creation, modification, or split

CREATE

The SPLIT will apply to both PNRs (the newly created one and the modified one in that process).

transaction_type

string

DIRECT, INDIRECT

Identifies whether the modification to the PNR is due to a direct intervention by a user/API or if the modification is indirect and related to another process.

origin

string

  • AGENT

  • WEBSERVICES

  • FROM_EXTERNAL_MESSAGE

  • INTERNAL_PROCESS

Identifies the origin that triggers the modification related to the transaction_type.

If it is DIRECT, this field could be:

  • AGENT → change from KiuCommand/some click scenarios

  • WEBSERVICES → change from WS/APIS/some click scenarios

  • FROM_EXTERNAL_MESSAGE → processing of TTY Type B/Type A messaging

If it is INDIRECT, this field could be:

  • INTERNAL_PROCESS → change affecting the booking due to an internal system process, such as robot time limit adjustments, service cancellations, etc.

  • FROM_EXTERNAL_MESSAGE → processing of TTY Type B messaging

application

string

  • KIU_COMMAND

  • OTHER

  • PRL_PROCESS

  • PFS_PROCESS

  • CONFIRM_WAITLIST_PROCESS

Detailed in "Source and Applications"

timestamp

datetime

2023-04-20T22:02:32.750Z

...