KIU SNAPSHOTS Documents (TKT/EMD/RFND)
- Daniela Salomon
- Ezequiel Rozenberg
- Nicolás Gauna
Introduction
KIU SNAPSHOTS Documents is a delivery service for document issuances and cancellations for any type of transaction, including TKT, EMD, RFND. In a second phase, document modifications will also be included.
This service allows for real-time retrieval of a copy of each issuance or void by sending a JSON file to the configured destination.
File Structure
The name of the generated JSON file has the prefix DOCUMENTS and UTC timestamp, resulting in the following pattern: DOCUMENTS_YYYYMMDDTHHMMSSFFFZ.json.
Internally, the file contains an “event_details” object that includes information about the event that generated the issuance, change, or cancellation of the document. Additionally, includes a list of documents document_list, where each object in the array represents an affected document and the schema of that document is specified in the API ticket_display_v2.
Example
{
"event_details": {
"system_from": "XX",
"company": "00XX",
"channel": "HOST",
"subchannel": "OFFICE SALES",
"device": "SST00XXG07",
"agent": "KIUHELPER",
"transaction_type": "DIRECT",
"origin": "AGENT",
"application": "KIU_COMMAND",
"timestamp": "2023-08-01T13:28:14.947Z",
"document_action": "ISSUE"
},
"document_list": [
{
"transaction_code": "TKTT",
"main_document_number": "9990210004401",
"plating_carrier": "XX",
"year_of_issue": 2023
....
}
]
}
Structure of event_details
The object event_details has the following structure:
Key | Data type | Possible values | Description | Example |
|---|---|---|---|---|
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’s the GDS code (C1, 1A, etc.). In the case of HOST, is the value configured in the office table, command DNO / BI STAT.SUB-CHANNEL. | SALES OFFICE |
device | string(0:10) |
| Kiu device that has generated the transaction | LPB00Z8205 |
agent | string(0:9) |
| Kiu device that has generated the transaction | HDQ00Z8SM |
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. |
|
document_action | string | ISSUE VOID SSR_TKNE_NOTIFICATION (pediente) REVALIDATE (pediente) STATUS_CHANGED (pediente) | Identify the action of the document | ISSUE |
origin | string |
| Identifies the origin affecting the document related to the If it is DIRECT, this field could be:
If it is INDIRECT, this field could be:
|
|
application | string |
| Detailed in "Source and Applications" |
|
timestamp | datetime |
| Date and time of file generation | 2023-04-20T22:02:32.750Z |
Source and Applications
Given the different scenarios where the status of document coupons can be issued or modified, they are classified based on the type of transaction - direct or indirect - the origin of the modification, and the application that triggered it.
Based on these variables, the following combinations are constructed:
origin | application | agent | descripción |
|---|---|---|---|
AGENT/WEBSERVICES | KIU_COMMAND / OTHER | The entity that generates the transaction | Issuance, void, and manual status change processes via commands or APIs |
WEBSERVICES | OTHER | The entity that generates the transaction | Issuance, void, and manual status change processes via webservices (v1 and v2) |
FROM_EXTERNAL_MESSAGE | SSR_TKNE_NOTIFICATION | KIUSYSTEM | Process of notification via Type B messaging. In this case, the device will be that of the office configured for the host with terminal address 00. |