Ticket

This guide will help you understand the NDC API workflow for getting ticket(s). Once you have paid and confirmed your booking, you can generate the ticket. The following endpoint is used in the workflow:

  1. AirDocIssue

To understand the process of booking, refer to:

What do you need to start?

To get started with generating ticket(s), you will require various payload data to process other requests. For completing the workflow, we recommend that you collect relevant information from the responses.

Step 1. Air Doc Issue

You can use this endpoint to generate the ticket. The Order ID and GDS Booking Reference (where GDS stands for Global Distribution System) are all required to complete the process.

Visit AirDocIssue endpoint to know more about air doc issue and the relevant parameters.

Core Query
curl --location --request POST 'http://newapi.tltid.com/AirDocIssue' \
--header 'Content-Type: application/json' \
--header 'Authorization: 2f2b265625d76a6704b08093c652fd791626187309' \
--data-raw '{
    "AirDocIssueRQ": {
        "Query": {
            "OrderID": "LZVRC19L",
            "GdsBookingReference": "MRYMXE"
        }
    }
}'

What will you get in return?

As a result of this request, you will get the ticket number and type. Below is a sample response to your order:

{        "TicketDocInfos": {
            "TicketDocInfo": [
                {
                    "TicketDocument": {
                        "TicketDocNbr": "2793737614806",
                        "Type": "TKT"
                    },
                    "PassengerReference": "ADT1",
                    "GdsBookingReference": "MRYMXE"
                }
            ]
        }
}'

Congratulations! You have completed the process of generating a ticket.