Skip to content

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 is expected to include the complete list of segments, both those that have been modified and those that remain unchanged. This ensures that TTN has a full and consistent view of the booking state.

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

ParameterTypeRequiredDescription
└ typeStringYesType for schedule changes callback - "schedule_changes"
└ orderNumStringYesUnique order number on the Partner side
journeys[Object]YesUpdated itinerary information
  └ segments[Object]YesSegment information
    └ sensitivityLevelStringYesType of segment modification (default: "0")
    └ marketingCarrierStringYesMarketing Carrier [IATA airline code]
    └ flightNumIntegerYesFlight Number
    └ departureStringYesDeparture [IATA airport code]
    └ arrivalStringYesArrival [IATA airport code]
    └ departureDateStringYesDeparture Date [yyyy-MM-dd](Local time of departure location)
    └ departureTimeStringYesDeparture Time [HH:mm](Local time of departure location)
    └ arrivalDateStringYesArrival Date [yyyy-MM-dd](Local time of arrival location)
    └ arrivalTimeStringYesArrival Time [HH:mm] (Local time of arrival location)

Explanation of sensitivityLevel values

  • "0" – Changes that do not require passenger acceptance
  • "1" – Changes that require passenger acceptance
  • "2" – Cancellation that requires passenger acceptance

Request Example

json
{
  "type": "schedule_changes",
  "orderNum": "917685547687690201",
  "journeys": [
    {
      "segments": [
        {
          "sensitivityLevel": "0",
          "marketingCarrier": "W9",
          "flightNum": "5772",
          "equipment": "JET",
          "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

ParameterTypeRequiredDescription
└ successBooleanYesHandling status. Success issue - true. Failed issue - false
└ messageStringNoInfo message (returned only when success = false; contains error details)

Success Response Example

json
{
  "success": true
}

Failed Response Example

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

TTN Octo API documentation