AirTicketing Workflow

The TicketIssue API tickets a booked PNR. It uses a workflow of multiple calls to create a workbench, issue payment, and commit the workbench to ticket the PNR.

This topic details the requests and responses in the AirTicketing workflow, from creating the workbench through issuing the ticket. For a listing of objects in the requests and responses, see the AirTicketing API Reference.

The Travelport JSON APIs support several book and ticketing workflow options. See Reservation and Ticketing Workflows for a summary of all options.

This topic details the requests and responses in the AirTicketing workflow, from creating the workbench through issuing the ticket. For a detailed listing of all objects, see the AirTicketing API Reference.

Additional options:

In this topic:

AirTicketing Workflow

The AirTicketing workflow uses the following HTTP requests summarized in the following table and detailed below.

Step Type of request Notes

Create a reservation workbench

POST

First mandatory step in the workflow. Requires a POST request with the reservation locator from the AirReservation commit response.

Returns an identifier for the workbench. This identifier is sent in every subsequent POST request in the workflow.

Add form of payment details

POST

Required if not added as part of the reservation workflow.

Returns a confirmation identifier.

Commit payment

POST

Required (except for ticketless carriers) if not added as part of the reservation workflow.

Returns a confirmation identifier.

Commit the workbench and issue the ticket

POST

Final step in the ticketing workflow. Issues the ticket (and EMD if applicable), discards the workbench, and returns a ticket number.

Create Workbench with PNR

The first step is to create a reservation workbench, which generates an empty workbench container with a workbench ID.

To establish the workbench, send a POST request with the PNR locator code to the following resource; see Air API Endpoints for the endpoint.

POST /buildfromlocator?Locator={PNR}

The message payload sends a blank ReservationID object per below.

{
    "ReservationID": {
                
    }
}

The response returns itinerary details and is the same as for a PNR Retrieve, plus a workbench ID in an additional Identifier object at the end of the response. The following excerpt shows a workbench ID. This workbench ID must be sent in all subsequent requests in the workflow.


   ...
        "Identifier": {
            "authority": "Travelport",
            "value": "7c67fa06-08ec-4d01-b7f4-c203cf542a3a"
        }

Add Form of Payment

The next step is to add form of payment (FOP) details to the workbench, if FOP was not added in the reservation workflow. If FOP was added during the AirReservation Workflow (supported only for GDS), that information is retrieved during ticketing. Skip to the Add Payment step.

Either cash or credit card FOP is supported.

{
    "FormOfPaymentPaymentCard": {
        "id": "formOfPayment_5",
        "FormOfPaymentRef": "formOfPayment_5",
        },
        "PaymentCard": {
            "@type": "PaymentCardDetail",
            "id": "paymentCard_4",
            "expireDate": "0521",
            "CardType": "Credit",
            "CardCode": "VI",
            "CardHolderName": "JANE DOE",
            "CardNumber": {
                "@type": "CardNumber",
                "PlainText": "4987654321098769"
            },
            "SeriesCode": {
                "PlainText": "123"
            },
        }
    }
}

The response returns a confirmation identifier. The value returned has no subsequent use in the workflow at this time.

Add Payment

The Add Payment step sends the payment. It references both the form of payment and the offer. At this time only one FOP is supported in the payment request.

The message payload includes identifiers for the form of payment and offer.

Commit (Issue Ticket)

After submitting payment, commit the workbench and issue the ticket. There is no message payload.

Back Office Accounting

To update any back office accounting systems with ticket information at the time of ticketing, send the Issuance query parameter with a value of BACKOFFICE when you commit the workbench in the ticketing workflow.

The ticket can have already been issued, or not issued yet. If payment has been added to the workbench, a ticket will be issued. The Issuance parameter can be sent without payment information to send a message to update the back office system and discard the workbench but not yet issue the ticket.

The response returns an interface control number.