1. ScheduleChangeNotify
PKFARE Flight Buyer API
  • Guides
    • Quick Start
    • Tricks for Playing with PKFARE API
    • Book air tickets with ancillaries
    • Raise refund requests
    • Raise change requests
    • Receive flight rescheduled notification
    • Add Paid Bags after the Booking
    • Branded Fare Integration Guide
  • API Reference
    • Air ticket booking APIs
      • TicketIssuanceNotify_V2
      • Shopping V10
      • PrecisePricing V12
      • Penalty V4
      • PreciseBooking V8
      • CancelOrder
      • OrderPricing V6
      • Ticketing
      • OrderDetail V14
      • RequestTicketing
      • ModifyOrderStatus
    • Ancillary booking APIs
      • AncillaryStatusPush
      • AncillaryPricing V6
      • AncillaryBooking
      • CancelAncillaryOrder
      • AncillaryTicketing
      • AncillaryOrderDetail
    • Flight schedule change APIs
      • ScheduleChangeNotify
      • GetScheduleChangeReply
      • GetScheduleChangeList
      • AcknowledgeScheduleChange
      • AcceptScheduleChange
    • Refund APIs
      • RefundResultNotify
      • ReimbursedResultNotify
      • Refund Pricing
      • CheckRefundPricing
      • RefundRequest
      • CheckRefund
      • CheckReimbursed
      • DownloadAttachmentFile API
      • UploadAttachmentFile API
    • Change APIs
      • ChangeResultPush
      • Change Reshop
      • Change Request
      • Change Passenger Info
      • Change Reprice
      • ChangeRepricePush
    • Void APIs
      • ReimbursedResultPush
      • VoidRequest
    • Cache APIs
      • CacheShopping
      • ValidateItinerary API
    • APIs with all versions
      • CheckInInfoPush
      • Raise change requests Copy
      • Shopping
        • Shopping
        • Shopping_V2
        • Shopping_V4
        • Shopping V7
        • Shopping V9
        • Shopping V8
      • PrecisePricing
        • PrecisePricing
        • PrecisePricing_V2
        • PrecisePricing_V6
        • PrecisePricing V9
        • PrecisePricing V10
        • PrecisePricing V11
      • Penalty
        • Penalty
        • Penalty V2
        • Penalty V3
      • PreciseBooking
        • PreciseBooking
        • PreciseBooking_V2
        • PreciseBooking_V5
        • PreciseBooking V6
        • PreciseBooking V7
      • OrderPricing
        • OrderPricing_V2
        • OrderPricing V4
        • OrderPricing V5
      • Ticketing
        • Ticketing
      • TicketNumPush
        • TicketingNumPush
        • TicketingNumPush_V2
        • TicketingNumPush_V3
        • TicketIssuanceNotify
      • CancelOrder
        • CancelOrder
      • OrderDetail
        • OrderDetail_V2
        • OrderDetail_V3
        • OrderDetail_V4
        • OrderDetail_V5
        • Json_OrderDetail_V7
        • Json_OrderDetail_V8
        • OrderDetail V9
        • OrderDetail V13
      • AncillaryPricing
        • AncillaryPricing
        • AncillaryPricing V5
      • AncillaryBooking
        • AncillaryBooking
      • CancelAncillaryOrder
        • CancelAncillaryOrder
      • AncillaryTicketing
        • AncillaryTicketing_V2
      • AncillaryStatusPush
        • AncillaryStatusPush
      • AncillaryOrderDetail
        • AncillaryOrderDetail
      • RequestTicketing
        • RequestTicketing
      • ScheduleChangeNotify
        • ScheduleChangeNotify
      • GetScheduleChangeList
        • GetScheduleChangeList
      • AcknowledgeScheduleChange
        • AcknowledgeScheduleChange
      • AcceptScheduleChange
        • AcceptScheduleChange
      • GetScheduleChangeReply
        • GetScheduleChangeReply
      • RefundPricing
        • RefundPricing
      • CheckRefundPricing
        • CheckRefundPricing
      • RefundRequest
        • RefundRequest
      • RefundResultNotify
        • RefundResultNotify
      • CheckRefund
        • CheckRefund
      • ReimbursedResultNotify
        • ReimbursedResultNotify
      • CheckReimbursed
        • CheckReimbursed
      • UploadAttachmentFile
        • UploadAttachmentFile
      • DownloadAttachmentFile
        • DownloadAttachmentFile
      • ChangeReshop
        • ChangeReshop
      • ChangeRequest
        • ChangeRequest
      • ChangePassengerInfo
        • ChangePassengerInfo
      • VoidRequest
        • VoidRequest
        • VoidRequest_V2
      • ReimbursedResultPush
        • ReimburseResultPush_V2
  • Development Instructions
    • Signature
    • Order Status Explanation
    • Booking errors explanation and suggestions
    • Price Breakdown Explanation
    • Airlines available from PKFARE
    • PKFARE Operation Notice
    • How to retrieve airlines'PNR and ticket numbers
    • PKFARE Buyer API solutionId Usage Guide
  • Notice
    • Release Note
  • Schemas
    • Schemas
      • ShoppingReq
      • Result«ShoppingResult»
      • Authentication
      • SearchDTO
      • JourneysDTO_1
      • PassengersDTO
      • ShoppingResult
      • SegmentsDTO
      • SolutionsDTO
      • BaggageDTO
      • ConditionsDTO
      • ChangeDTO
      • OtherDTO
      • RefundDTO
      • JourneysDTO
      • SegmentInfoDTO
  1. ScheduleChangeNotify

ScheduleChangeNotify

1 Document Description#

1.1 Function Description#

After the order is generated, the airline may send the flight change information. Types of message include:
Flight cancelled
Flight cancelled, with protected flight(s)
Flight schedule changed, it could be time change, equipment change, terminal change, etc.
This API could push the schedule change information to your endpoint, once there is a schedule change happened.
If you will integrate this API, please kindly provide a reception service URL based on HTTP/HTTPS protocol to PKFARE. And we will pre-set it in the system.
Note:The schedule change notifify will send the flight information on changed flights. If booking is a round trip, and the schedule change happened for outbound flights, then only outbound flights will be in this request.

1.2 Target Reader#

The ScheduleChangeNotify API document targets developers who work in the fields of network development, maintenance as well as management. They should have the knowledge of at least one of the following programming languages: ASP, PHP, JAVA, ASP.NET or SQL.

1.3 Character Encoding#

The character code of this API is UTF-8.

1.4 Invoking Address#

This address URL is provided by the buyer partners.

1.5 Request Type#

POST

1.6 Request Header#

keyvalue
Content-Typeapplication/json;charset=UTF-8

2.Request Parameter#

This request is sent by PKFARE API. The structure parameter is JSON format.

2.1 Parameter Construction#

2.1.1 Basic parameter#
NameTypeRequired or NotParameter DescriptionSample
orderNumStringYesPKFARE order number915690623484957501
buyerOrderStringNoBuyer partner's order number. If you would like to receive a buyerOrder, please send it in the request of preciseBooking API. The buyer order number will be record and send it back when schedule change happened.111111
messageIdStringYesPKFARE message id2222222
messageCreateTimeStringYesSchedule change message create time [ yyyy-mm-dd hh:mm:ss],Beijing Time(GMT+8)2023-02-21 19:15:10
sensitivityLevelStringYesMessage sensitivity level:
0-This level is not eligible to request involuntary refund or changes, and it is not required to be accepted by passenger.
1-This level may not be eligible to request involuntary refund or changes, but it is required to be accepted by passenger.
2-This level is eligible to request involuntary refund or changes and it is required to be accepted by passenger.
0
orderPnrStringYesPNR of this order, the booking reference of reservation systemY78UJK
orderAirlinePnrStringYesAirline PNR of this order, the booking reference of airline systemCX/8IJ7LN
pnrListArrayNoPNR List of this order.Refer to 2.1.2.-
passengersArrayYespassengers of this order. Refer to 2.1.3.-
originFlightListArrayYesJourney and segment information before this schedule change. Refer to 2.1.4.-
changeFlightListArrayNoJourney and segment information after this schedule change. Refer to 2.1.5.-
2.1.2 PnrList#
NameTypeRequired or NotParameter DescriptionSample
segmentNoIntegerYesThe segment sequency of the journey1
departureStringYesDeparture airport code, 3 letters IATA codeHKG
arrivalStringYesArrival airport code, 3 letters IATA codeBKK
flightNumStringYesFlight number, format:Airline code and flight numberCX618
cabinClassStringYesCabin class. Refer to 4.1ECONOMY
bookingCodeStringYesBooking codeE
pnrStringNoPNR of this segment, the booking reference of reservation system. It will be blank if the reservation made for the whole order.Y78UJK
airPnrStringNoPNR of this segment, the booking reference of airline system. It will be blank if the reservation made for the whole order.CX/8IJ7LN
ticketNumsArrayNoPassesger and ticket number information. Refer to 2.1.8.-
2.1.3 Passengers#
NameTypeRequired or NotParameter DescriptionSample
lastNameStringYesLast namewang
firstNameStringYesFirst namejia
birthdayStringYesDate of birth [yyyy-mm-dd]1988-10-10
sexStringYesGender, M - male, F - Female. Refer to 4.4M
psgTypeStringYesADT - adult, CHD - child , INF-Infant. Refer to 4.3CHD
cardTypeStringNoTravel document type. Refer to 4.2P
cardNumStringNoTravel document numberP78921345
cardExpiredDateStringNoTravel document expiration date, [yyyy-mm-dd]2025-03-03
nationalityStringYesNationality of the passenger, 2 letters country codeCN
ticketNumStringNoTicket number. If multiple ticket numbers, it will be separted by slash[/]9991234567890/9991234567891
2.1.4 OriginFlightList#
NameTypeRequired or NotParameter DescriptionSample
journeysArrayYesJourney information. Refer to 2.1.6.-
2.1.5 changeFlightList#
NameTypeRequired or NotParameter DescriptionSample
journeysArrayYesJourney information. Refer to 2.1.6.-
2.1.6 journeys#
NameTypeRequired or NotParameter DescriptionSample
journeySeqIntegerYesJourney sequency, outbound refer to 1, inbound refer to 2.1
segmentsArrayYesflight information. Refer to 2.1.7.-
2.1.7 segments#
NameTypeRequired or NotParameter DescriptionSample
airlineStringYesAirline codeCX
flightNumStringYesFlight number618
equipmentStringYesEquipment code777
cabinClassStringYesCabin class. Refer to 4.1ECONOMY
bookingCodeStringYesBooking codeE
departureStringYesDeparture airport code, 3 letters IATA codeHKG
arrivalStringYesArrival airport code, 3 letters IATA codeBKK
departureTerminalStringNoDeparture terminal1
arrivalTerminalStringNoArrival terminal1
departureDateStringYesDeparture date, [yyyy-mm-dd], local time of departure city2025-03-03
arrivalDateStringYesArrival date, [yyyy-mm-dd], local time of arrival city2025-03-03
departureTimeStringYesDeparture time, [hh:mm],local time of departure city10:10
arrivalTimeStringYesArrival time, [hh:mm], local time of arrival city10:10
flightTimeIntegerYesFlight time, unit: minutes890
stayTimeIntegerNoStay time for stopover flight, unit: minutes120
codeShareStringYesCode share flight flag, Y - Code share flight, N - Not code share flightN
opFltNoStringNoOperation flight number160
opFltAirlineStringNoOperation airlineKA
stopoverStringNoStopover airport code, 3 letters IATA codeCNX
messageTypeStringNoMessage type:
1-Flight changed
2-Flight canceled with protect flight
3-Flight canceled
4-Flight resumted.
5- Flight overbooking.
For type 3, 4 and 5, there is no ChangeFlightList information.
1
2.1.8 ticketNums#
NameTypeRequired or NotParameter DescriptionSample
ticketNumStringNoTicket number-
lastNameStringYesLast namewang
firstNameStringYesFirst namejia
birthdayStringYesDate of birth [yyyy-mm-dd]1988-10-10
sexStringYesGender, M - male, F - Female. Refer to 4.4M
cardTypeStringNoTravel document type. Refer to 4.2P
cardNumStringNoTravel document numberP78921345

2.2 Request Sample#

2.2.1 JSON request sample#
{
    "messageId": "2944695",
    "messageCreateTime": "2023-02-22 15:07:10",
    "orderAirlinePnr": "CX/WCK5N6|AA/HMMRAK",
    "orderNum": "916727111389870001",
    "buyerOrder":"10387629"
    "orderPnr": "HMMRRJ",
    "sensitivityLevel": "1",
    "changeFlightList": [
                {
                    "airline": "AA",
                    "arrival": "DFW",
                    "arrivalDate": "2023-12-03",
                    "arrivalTime": "16:50",
                    "bookingCode": "C5",
                    "cabinClass": "FIRST",
                    "codeShare": "N",
                    "departure": "HKG",
                    "departureDate": "2023-11-24",
                    "departureTime": "14:20",
                    "equipment": "77W",
                    "flightNum": "126",
                    "stayTime": 0,
                    "stopover": ""
                }
            ]
        }
    ],
    "originFlightList": [
        {
            "journeySeq": "1",
            "segments": [
                {
                    "airline": "AA",
                    "arrival": "DFW",
                    "arrivalDate": "2023-12-02",
                    "arrivalTime": "16:50",
                    "bookingCode": "C5",
                    "cabinClass": "FIRST",
                    "codeShare": "N",
                    "departure": "HKG",
                    "departureDate": "2023-11-26",
                    "departureTime": "14:20",
                    "equipment": "77W",
                    "flightNum": "126",
                    "messageType": "2",
                    "stayTime": 0,
                    "stopover": "",
                    "messageType":2
                }
            ]
        }
    ],
    "passengers": [
        {
            "birthday": "2003-02-12",
            "cardExpiredDate": "2025-02-05",
            "cardNum": "89374924",
            "cardType": "PP",
            "firstName": "BLAKE",
            "lastName": "HUBBARD",
            "nationality": "US",
            "psgType": "ADT",
            "sex": "M",
            "ticketNum": "0063742676484"
        },
        {
            "birthday": "2003-04-01",
            "cardExpiredDate": "2025-03-25",
            "cardNum": "293874123",
            "cardType": "PP",
            "firstName": "DARRYL",
            "lastName": "COX",
            "nationality": "US",
            "psgType": "ADT",
            "sex": "F",
            "ticketNum": "0063742676484"
        }
    ]
}

3. Response Parameter#

This response is returned by the buyer partners. Please respond in the format we provided below. Otherwise system is not able to recognize the response. If the response is not with 'errorCode' 0, it will be recognized as failed.

3.1 Response Parameter Contruction#

NameTypeParameter DescriptionSample
errorCodeStringError code0
errorMsgStringError messageOK

3.2 Response Sample#

3.2.1 Normal Response#
{
    "errorCode":"0",
    "errorMsg":"ok"
}
3.2.2 Error Response#
{
    "errorCode": "1",
    "errorMsg": "Failure reason",
}

4 Appendix#

4.1 Cabin Class#

EnumDescription
ECONOMYEconomy Class
PREMIUM ECONOMYPremium Economy Class
BUSINESSBusiness Class
FIRSTFirst Class

4.2 Type of Travel Document#

EnumDescription
PPassport
NChinese Identity
OOthers

4.3 Passenger Type#

EnumDescription
ADTadult
CHDchildren[2-12 years old]

4.4 Gender#

EnumDescription
MMale
FFemale
Top
Modified at 2024-05-06 02:01:46
Previous
RequestTicketing
Next
GetScheduleChangeList