Tickets inserted through the Ticket API can be attached to a transport product in Qondor by Project Managers, and can also be included in invoicing using the Invoice API.


If the ticket metadata contains a Qondor project number it will automatically be listed in the "Attach tickets" dialogue in any transport product in the project. You can Search by ticket number, PNR or traveller name. If the ticket for some reason isn't connected to the project you need to check the "Include tickets not linked to this project" box:

After adding the ticket to the transport product you're able to adjust the sales price:


  • It is also possible to insert the travel class via the API. The input field will suggest the following classes: Economy, Business, First, 1st and 2nd.
  • If a product has a ticket attached, then the ticket icon will appear next to the product. This helps Project managers to easily identify which products have tickets attached from Offer admin. If you hover over the icon, a popup will appear where you can see if the price on the ticket matches the product price.
Screenshot of Qondor Offer admin with ticket icon and products

Screenshot from Offer admin


Upon invoicing the transport product Qondor will verify that the product and ticket(s) out price(s) match:

The appendix (ticket information) will be included in the API response if you choose so when creating the invoice specification:

An excerpt of the Invoice API response with a ticket appendix:

When the product is successfully invoiced, a locked padlock icon will show so that Project managers can identify invoiced products.


The flowchart below describes how Qondor handles tickets all the way from inserting them through the Ticket API until the invoiced transport product is available in the Invoice API.

Did this answer your question?