Skip to main content

Update Itinerary

Travel Agency
Airline Carrier

Add Secure Flight Information

Add Secure Flight Information

DOCS can only be added to the UpdateReservationRQ request via the SpecialServiceRequestUpdate element. This is done by specifying DOCS as the SSR and adding the full text of the SSR in the Text child element. Follow the template below:

DB/(date of birth DDMMMYY)/(gender code F,M,X, FI, MI)/(last name)/(first name)

  • Request
    <UpdateReservationRQ xmlns="" xmlns:or="" Version="1.19.0" EchoToken="RK/ENV/PXGSSDMLT-60703">
        <ReturnOptions IncludeUpdateDetails="true" RetrievePNR="true" />
            <ReservationUpdateItem UpdateId="1">
                <SpecialServiceRequestUpdate op="C" type="H">
  • Response
    <stl19:UpdateReservationRS xmlns:stl19="" xmlns:ns6="" xmlns:or114="" xmlns:raw="" xmlns:ns4="" Version="1.19.0">
        <stl19:Reservation numberInParty="0" numberOfInfants="0" NumberInSegment="0">
                <stl19:FlightsRange Start="2021-05-25T06:57:00" End="2021-05-25T10:00:00"/>
            <stl19:POS AirExtras="false" InhibitCode="U">
                <stl19:Source BookingSource="A0A0" PseudoCityCode="xxxx" AirlineVendorID="AA" HomePseudoCityCode="xxxx" PrimeHostID="1S"/>
                    <stl19:Passenger id="3" nameType="S" passengerType="ADT" nameId="01.01" nameAssocId="1" elementId="pnr-3.1">
                                <stl19:DOCSEntry id="9" type="A">
                    <stl19:Segment sequence="1" id="8">
                        <stl19:Air id="8" sequence="1" segmentAssociationId="3" isPast="false" DayOfWeekInd="2" CodeShare="false" SpecialMeal="false" SmokingAllowed="false" ResBookDesigCode="G">
                            <stl19:OperatingAirlineShortName>AMERICAN AIRLINES</stl19:OperatingAirlineShortName>
                            <stl19:Banner>MARKETED BY AMERICAN AIRLINES</stl19:Banner>
                <or114:OpenReservationElement id="9" type="SRVC" elementId="pnr-9">
                    <or114:ServiceRequest actionCode="HK" airlineCode="AA" code="DOCS" serviceCount="1" serviceType="SSR" ssrType="AFX">
                        <or114:FullText>DOCS AA HK1/DB/03MAR90/M/LASTNAME/NAME</or114:FullText>
            <stl19:UpdateResult UpdateId="1" Status="SUCCESS">
                <stl19:Item id="9" op="C"/>


What is Secure Flight information?

Secure Flight is a program developed by the United States Department of Homeland Security (DHS) in response to a key 9/11 Commission recommendation; uniform watchlist matching by the Transportation Security Administration (TSA). The mission of the Secure Flight program is to enhance the security of domestic and international commercial air travel through the use of improved watchlist matching.

What is included within the Secure Flight program?

Flight information includes airlines flying into, out of, within, or over the United States, as well as all point-to-point international flights operated by U.S.-based airlines. Secure Flight applies to all applicable PNRs, regardless of the sales channel the reservation was booked through.

What does watchlist matching mean?

Secure Flight matches the name, date of birth, and gender information for each passenger against government watch lists to:

  • Identify known and suspected terrorists
  • Prevent individuals on the "No Fly List" from boarding an aircraft
  • Identify individuals on the "Selectee List" for enhanced screening
  • Facilitate passenger air travel
  • Protect individuals' privacy

What fields are mandatory when entering Secure Flight Passenger Data (SFPD)?

TSA requires airlines to collect and transmit the following Secure Flight Passenger Data (SFPD). These data elements are stored in the IATA SSR standard: DOCS. This includes:

  • Passenger full name: as it appears on state or government ID used at the airport (state ID card, driver's license or passport)
  • Date of birth: must match the data on the document presented at the airport
  • Gender

Is the passenger's middle/second name mandatory when entering SFPD?

No. The second or middle name is an optional field, unless the official document the passenger presents upon check-in at the airport contains the middle/second name.

Is a prefix/suffix considered for SFPD match?

Prefix and suffixes in the PNR name field are not used when a name match is considered. If all other information is accurate in the PNR and SFPD, these scenarios will typically pass to allow check in.

Is Secure Flight information required for all passengers?

Yes. All passengers including minors (17 and under) must provide their full name, date of birth, and gender. The data provided must match the data on the document presented at the airport.

What happens with Secure Flight information if a passenger is a minor without ID?

If the individual is "under 18 years of age and does not have a verifying identity document, TSA may, on a case-by-case basis, authorize the minor or an adult accompanying the minor to state the individual’s full name and date of birth in lieu of providing a verifying document."

Do I need to include name titles when entering SFPD?

No. Even though the PNR name field may include a title (MR, MRS, MISS, MSTR, ESQ, DR, etc.), the title should not be added to the SFPD 3DOCS entry.

What data is optional when entering SFPD?

Optional Secure Flight data elements include:

  • Redress number: Unique identifier issued by DHS to those using the Traveler Redress Inquiry Program.
  • Known Traveler Number: Unique identifier for the Pre-Screening Pilot Program to expedite security processes for certain frequent fliers members and certain members of government approved Trusted Traveler programs such as: Global Entry, NEXUS, SENTRI.

What happens if the PNR is missing SFPD?

PNRs without full SFPD will be rejected by the TSA’s Secure Flight rule and will not be processed by TSA.

Do I need to add all needed SFPD before issuing tickets?

Yes. Once you add the appropriate Secure Flight data and it is updated in the airline system, you can issue the tickets.

You are allowed to use segment select or name select to ticket those passengers with associated Secure Flight data, leaving those without data unticketed. You can ticket the remaining passengers once their SFPD is added to the PNR.

How do I include SFPD for an infant with their own (purchased) seat?

  • Because a purchased seat requires a valid name field - even for infants - do not use the infant name indicators in your SFPD SSR request
  • Use the adult gender identifier of M for Male or F for Female

Which gender codes can be included when adding SFPD to the PNR?

Acceptable gender codes include:

  • M - Male
  • F - Female
  • MI - Male Infant
  • FI - Female Infant
  • U - Undisclosed

    Note: This gender code is valid for APIS and Secure Flight (SFPD) formats only.

  • X - Unspecified