ScheduleChange

  • Purpose: This interface is used to receive flight change notifications from suppliers, including flight delays, cancellations, changes, etc.
  • Request: POST
  • Encryption: No
  • FareMarket address:/supplier/v1/api/schedule_change

Request

Parameter Name Type Required Description
apiKey string ✅ Each supplier has its own unique apiKey, which is used to indicate the supplier’s identity. AeroHub provides it to the supplier before interface testing.
requestId string ✅ Request ID, which is unique for each call in the ticket issuance process and has a length of 32 digits.
purchaseOrderNo string ✅ AeroHub order number
ticketNo string ⬜️ Ticket number, if there is no low-cost airline, it can be consistent with PNRCode
changedTime string ✅ The time when the aircraft accident occurred. If you don’t know, you can pass the interface call time in ISO 8601 format.
changeType int ✅ Type of aviation accident: 1 flight cancellation, 2 flight change (including delay)
isChange bool ✅ Whether to change the route type (such as direct flight to transit, transit to direct flight): true changed, false unchanged
items array/items Element ✅ Aviation information

array/items Element

Parameter Name Type Required Description
segmentNo int ✅ Flight sequence, 1 outbound trip, 2 return trip
originalSegments array/originalSegments Element ✅ When the type is flight change: the complete itinerary information before the change, when the type is flight change cancellation: only the original flight information that has been canceled is transmitted
changedSegments array/changedSegments Element ⬜️ Complete segment information after flight change, changeType=2 (flight change) must be sent
array/originalSegments Element
Parameter Name Type Required Description
flightNumber string ✅ Flight number, such as: CA123
depAirport string ✅ Departure airport code, using IATA three-letter code as the standard
depTime string ✅ Departure date and departure time (local time) in ISO 8601 format
arrAirport string ✅ Arrival airport code, using IATA three-letter code as the standard
arrTime string ✅ Arrival date and arrival time (local time) in ISO 8601 format
array/changedSegments Element
Parameter Name Type Required Description
flightNumber string ✅ Flight number, such as: CA123
depAirport string ✅ Departure airport code, using IATA three-letter code as the standard
depTime string ✅ Departure date and departure time (local time) in ISO 8601 format
arrAirport string ✅ Arrival airport code, using IATA three-letter code as the standard
arrTime string ✅ Arrival date and arrival time (local time) in ISO 8601 format

Sample Request

{
    "apiKey": "PcrNq8964iFUkE0CyVV4bhgXXX",
    "requestId": "7a0091e344cc4a9886eafd4334d36bcb",
    "purchaseOrderNo": "F1783888564216623104",
    "ticketNo": "3DFCH0",
    "changedTime": "2024-05-07T15:28:28",
    "changeType": 2,
    "isChange": false,
    "items": [{
        "segmentNo": 1,
        "originalSegments": [{
            "flightNumber": "DD323",
            "depAirport": "UBP",
            "depTime": "2024-05-09T11:20",
            "arrAirport": "DMK",
            "arrTime": "2024-05-09T12:20"
            },
            {
            "flightNumber": "DD323",
            "depAirport": "UBP",
            "depTime": "2024-05-09T11:20",
            "arrAirport": "DMK",
            "arrTime": "2024-05-09T12:20"
            }],
        "changedSegments": [{
            "flightNumber": "DD323",
            "depAirport": "UBP",
            "depTime": "2024-05-09T11:30",
            "arrAirport": "DMK",
            "arrTime": "2024-05-09T12:30"
            }]
        }]
}

Response

Parameter Name Type Required Description
code int ✅ For the status code of AeroHub, refer to Market Errors in the general instructions.
msg string ✅ For AeroHub error instructions, refer to Market Errors in General Instructions.

Response Example

Success Response:

{
    "code": 200,
    "msg": "Successful"
}

Error Response

{
    "code": 400,
    "msg": "Failed"
}

Things to note

  • Please ensure you provide the correct booking number and flight information.
  • The time should beISO 8601Format.
  • sequence If it is a round trip, both the outbound and return journeys start from 1.
  • changedSegments It is only necessary to return when the aircraft changes.
Author：AeroHub  Create time：2024-03-15 09:56
Last editor：AeroHub  Update time：2026-10-20 11:28