Before you submit a ticket, check our Frequently asked questions; many answers are already there.

To submit a ticket, choose New Issue and select TKCONNECT (NDC). Then pick the category and sub-category that match your issue, describe it and submit:

• API Test and Integration: certification and integration questions before you go live.
• Commercial Issues: your application, updates to your agency card and users, and feedback on our processes.
• UI Error (Live Environment): problems in the TKCONNECT UI, from search and payment to changes, refunds and sales reports, including access problems.
• API Error (Live Environment): errors in your live API connection, by API (Offer, Order, Servicing, Ancillary) or in order change notifications.
• Request and Suggestion: passenger service requests, such as seat selection, wheelchair assistance, travel document (DOCS) updates, duplicate tickets or offloads, and your suggestions for TKCONNECT.

Depending on the category, the form asks for details such as the Offer ID or origin and destination, correlation ID, sales branch ID, transaction ID or XML logs, so have them ready. Add screenshots for UI issues and the timestamp for API issues. Before you share logs or screenshots, remove or mask credentials, API keys, tokens and payment card data, and send files only through the Issue Tracking Panel or the Report Error button in the TKCONNECT UI. You can follow your tickets under My Issues."

Connected through an aggregator? Contact your aggregator first. If your aggregator cannot resolve the issue, submit a ticket with us.

Service every TKCONNECT booking through TKCONNECT only. Changes made through a GDS or another channel put the order and the PNR out of sync. If you cannot complete a servicing action in your channel, submit a ticket under Request and Suggestion.