Schedule Change Notify

The partner can send to the TTN system information regarding changes to an existing booking in order for TTN to notify passengers accordingly.

The journeys field must contain the complete itinerary, including all segments associated with the booking, regardless of whether a segment has been modified. Both modified and unchanged segments must be provided. This ensures that TTN has a complete and consistent view of the booking and can correctly process the update.

Each segment may carry its own type of change, which should be indicated via the sensitivityLevel field.

Endpoint

Method: POST

URL: Webhook URL - TTN will send the Webhook URL in the /json/preciseBooking request - notifyUrl input parameter.

Request Parameters

Parameter	Type	Required	Description
└ type	String	Yes	Type for schedule changes callback - "schedule_changes"
└ orderNum	String	Yes	Unique order number on the Partner side
└ journeys	[Object]	Yes	Updated itinerary information
└ segments	[Object]	Yes	Segment information
└ sensitivityLevel	String	Yes	Type of segment modification (default: "0")
└ marketingCarrier	String	Yes	Marketing Carrier [IATA airline code]
└ flightNum	Integer	Yes	Flight Number
└ departure	String	Yes	Departure [IATA airport code]
└ arrival	String	Yes	Arrival [IATA airport code]
└ departureDate	String	Yes	Departure Date [yyyy-MM-dd]（Local time of departure location）
└ departureTime	String	Yes	Departure Time [HH:mm]（Local time of departure location）
└ arrivalDate	String	Yes	Arrival Date [yyyy-MM-dd]（Local time of arrival location）
└ arrivalTime	String	Yes	Arrival Time [HH:mm] （Local time of arrival location）

Explanation of sensitivityLevel values

Value	Description
"-1"	Segment remains unchanged
"0"	Segment is changed without requiring passenger acceptance
"1"	Segment is changed and requires passenger acceptance
"2"	Segment is cancelled and an alternative segment is provided requiring passenger acceptance
"3"	Segment is cancelled without an alternative segment and details of the cancelled segment are provided

Request Example

{
  "type": "schedule_changes",
  "orderNum": "917685547687690201",
  "journeys": [
    {
      "segments": [
        {
          "sensitivityLevel": "0",
          "marketingCarrier": "W9",
          "flightNum": "5772",
          "departure": "IST",
          "arrival": "LGW",
          "departureDate": "2026-08-14",
          "departureTime": "16:40",
          "arrivalDate": "2026-08-15",
          "arrivalTime": "18:55"
        }
      ]
    },
    {
      "segments": [
        {
          "sensitivityLevel": "-1",
          "marketingCarrier": "W9",
          "flightNum": "5729",
          "departure": "LGW",
          "arrival": "IST",
          "departureDate": "2026-08-22",
          "departureTime": "10:20",
          "arrivalDate": "2026-08-22",
          "arrivalTime": "16:30"
        }
      ]
    }
  ]
}

Response Parameters

Parameter	Type	Required	Description
└ success	Boolean	Yes	Handling status. Success issue - true. Failed issue - false
└ message	String	No	Info message (returned only when success = false; contains error details)

Success Response Example

{
  "success": true
}

Failed Response Example

{
  "success": false,
  "message": "Order number is not found"
}