Log Download
The third party suppliers(GDS,LCC, H2H) communication logs will be required to be downloaded by Travel Agents(Travlinq integrators) for their ticketed bookings. Hence, Travlinq will provide a APi end point for download the communication logs
Logs available duration
The user is able to download complete logs within 90 days after a transaction is done. After 90 days, users are able to download ticketed bookings(search to book)logs only. The day(90) count is configurable. That will be decided by travlinq API team based on the log filling rate.
Logs file naming convention
| Naming Option | Description |
|---|---|
By conversationId |
If the user downloads by using the conversationId , the zip file name will be generated in the below format. conversationId_logs_currentDate Ex : 7c749d95-3879-488e-ae4a-4d78e4ed2d3a_Logs_2023-05-29. |
By bookingReferenceId |
If the user download by using the bookingReferenceId , the zip file name will be generated in the below format. bookingReferenceId_Logs_currentDate Ex : BKR-2023-004437_Logs_2023-05-30 . |
- If booking has multiple conversation IDs, a final zip file is generated with set of zip files for each conversationId logs.
Log Download Use cases
There are few use cases which need to be considered when downloading logs as given below.
| Use Case | Description |
|---|---|
| Search to Book | All supplier logs (search to book) will be considered. |
| Re-initiate | All supplier logs which are initial search to book and logs related to re-initiate flow. |
| Re-issue booking | All supplier logs for each re-issue attempt (search to book). Each re-issue will have a different CID. Hence if a client can send only one CID then we will give logs only related to that CID. If the client will send a booking id then we will give all logs which belong to all conversations ids in the booking. |
| Post ancillary adding | All supplier logs which belong to search to book and adding post ancillary operation logs as well. |
| Cancellation | All supplier logs which belong to search to book and adding cancellation operation logs as well cancellation as well. |
| Travlinq logs | If client is required Travlinq API logs as well then that is also can be provided with any of above work flow. |
Log Download API
This service method is used to download the communication logs.You must send a conversationId or bookingReferenceId to download logs. You are able to send only one additional filter section on request. Response coming as a zip file.
Log Download API Request
| Tags | Attribute | Description |
|---|---|---|
| logDownloadCriteria | (JsonObject) | |
| bookingReferenceId (String) |
Identifies the booking after the booking creation | |
| conversationId (String) |
conversationId of the relevant transaction | |
| includeApiLogs (Boolean) |
Whether downloading supplier logs only or both travlinq and supplier logs . if this is true then can get download travlinq + supplier logs as well. If this is false then can download only supplier logs. |
|
| flightFilters | (JsonObject) | |
| includeReissueAllLogs (Boolean) |
Download ticket logs only or download reissued all logs | |
| includeFlightCancellationLogs (Boolean) |
Download logs with cancellation logs or without | |
| additionalProperties (JsonObject) |
||
| hotelFilters | (JsonObject) | |
| includeHotelCancellationLogs (Boolean) |
Download logs with cancellation logs or without | |
| additionalProperties (JsonObject) |
||
| carFilters | (JsonObject) | |
| includeCarCancellationLogs (Boolean) |
Download logs with cancellation logs or without |
- Additional filters (flight,hotel and car) will be used when logs are downloaded by using bookingReferenceId. Otherwise, additional filters are not required for when use conversationId.
Log Download API Response
User able to download logs as zip file (Response coming as zip file byte array)
Sample downloaded zip file content (figure 01).
