Amadeus TTD Command: Set Confidential TST Flag

A complete guide to the TTD command in Amadeus — how to set the confidential flag on a TST and restrict its visibility according to Amadeus security settings.

TTD is not available to every agent by default. Before attempting to set the confidential flag on a TST, make sure the following conditions are met:

• Office-level security rights — your Amadeus office profile must include the TST confidentiality feature. Without it, the TTD entry will be rejected by the system.
• Agent permissions — your individual sign-in must have permission to modify TST records. Restricted agents (view-only or limited ticketing profiles) cannot set or remove the confidential flag.
• Retrieved PNR with an active TST — the PNR must contain a valid TST. If no TST exists, TTD has nothing to apply the flag to.
• Supervisor or office authorization — in many agencies, the confidential flag is reserved for senior staff. Confirm your internal policy before using it.
• Correct office sign-in — the flag is applied at the office level. If you are working in a different office sign than the one that created the TST, the command may not apply as expected.

If any of these conditions is not met, contact your Amadeus office administrator or supervisor to adjust your security profile.

TTD is the Amadeus GDS command used to set the confidential flag on a TST (Transitional Stored Ticket).

Category: Ticketing.

The TTD command marks the TST as confidential, restricting its visibility according to the applicable Amadeus security settings.

This does not change the fare, taxes, or any other element of the ticket record — it only controls who can see the stored TST information. The confidential flag is applied at the office level and follows the security permissions defined in your Amadeus profile.

Enter the command while the PNR with the relevant TST is retrieved:

TTD

This sets the confidential TST flag on the ticket record in the PNR. End the transaction with ER to save the change.

• Visibility of the TST — agents without the required security permissions may not be able to display the record.
• Access to stored pricing — fare, taxes, fare basis, and form of payment can be hidden from unauthorised users.
• Office-level control — the flag works together with the security settings defined in your Amadeus office profile.
• No change to the ticket itself — the fare, itinerary, and issuance status remain exactly the same.

💡 Pro-Tip — How to Verify the Confidential Flag Was Applied

After saving the TTD entry, use the following verification sequence to confirm the flag was correctly applied:

1️⃣ TQT       → display the TST after TTD
2️⃣ check TST     → confirm the confidential flag is visible
3️⃣ ER        → save the transaction
4️⃣ sign-in test   → verify from an account without permissions

A properly flagged TST will show a confidential indicator when displayed with TQT or TQTC. If you cannot see it, check that the transaction was ended and that your office security profile supports the flag.

For an additional sanity check, ask a colleague whose profile has restricted TST access to retrieve the PNR and attempt to display the TST. If the flag is correctly set, access should be denied or the record should be hidden.

Use TTD when you need to mark a TST as confidential for security or privacy purposes. Typical scenarios include:

• Corporate or VIP bookings where pricing details must remain private.
• Tickets with negotiated or confidential fares that should not be widely visible.
• Internal agency pricing that should not be displayed to all staff.
• PNRs handled by specific departments with restricted access rights.
• Any case where privacy of ticket information is required by company policy.

A typical ticketing session using TTD might look like this:

• Retrieve the PNR and display the TST with TQT or TQTC.
• Complete any necessary updates to the ticket record.
• Enter TTD to set the confidential flag on the TST.
• End the transaction with ER to save the change.
• Verify with an authorised account that the TST is correctly restricted.
• Continue with issuance or any further processing as required.

• TTD → sets the confidential flag on a TST.
• TQT / TQTC → display the TST in formatted or cryptic mode. Read the full TQT guide.
• TTH → displays the history of changes made to a TST. Read the full TTH guide.
• TTC → creates a manual TST. Read the full TTC guide.
• TTK → manually updates fare, tax, and total elements. Read the full TTK guide.
• TTI → manually updates validity, baggage, fare basis, and fare calculation. Read the full TTI guide.
• TTF → removes the PNR change flag from one or more TSTs. Read the full TTF guide.
• TTE → deletes one or more TSTs from the PNR. Read the full TTE guide.
• TTS / TTA → split passengers from or add passengers to a TST. Read the TTS guide.

Explore the related Amadeus ticketing commands below to complete your TST toolkit:

What does TTD do in Amadeus?

TTD sets the confidential flag on a TST, restricting its visibility according to Amadeus security settings.

Does TTD change the fare or ticket data?

No. TTD only controls the visibility of the TST. The fare, taxes, itinerary, and issuance status remain exactly the same.

Who can view a confidential TST?

Only agents whose Amadeus profile permissions allow them to view confidential TSTs. Visibility depends on your office’s security settings.

Why is my TTD entry rejected?

The most common reason is that your office security profile does not include the TST confidentiality feature, or your individual sign-in lacks permission to modify TST records. Contact your Amadeus office administrator to adjust the security settings.

🔖

Save This Guide for Quick Reference

TTD is one of those commands you only need occasionally — but when you need it, you need it fast. Bookmark this page so you have the syntax, prerequisites and verification steps at your fingertips the next time a confidential booking comes across your desk.

Press Ctrl + D (Windows) or ⌘ + D (Mac) to add it to your bookmarks.