API Description Page

Overview

The SITA Advance Flight Delay Notification API provides real-time notifications on flight delays, enabling users to stay informed about delays or potential delays for arrival flights impacted by delays at departure airports. This API is designed to support proactive decision-making and improved resource planning.

Using the SITA Advance Flight Delay Notification API, users can subscribe to receive delay updates for arriving flights at specific airports.

This API focuses exclusively on advanced delay notifications. By delivering alerts directly over HTTP/HTTPS, it eliminates the need for repeated polling, saving time and resources.

The API provides real-time answers to critical questions, including:

Is a specific arrival flight delayed at a particular airport?
What is the estimated arrival time for a delayed flight?

This API ensures the relevant Stakeholders in the Air Transport Industry are better equipped to manage and respond to flight delays effectively and efficiently.

1 Revision History

Date	Document Version	Description
`20 January 2025`	`1.0`	`Initial version`
`25 March 2025`	`1.1`	`Appendix, Payload Documentation and Examples`
`26 March 2025`	`1.2`	`SITA Advance Flight Delay Notification API Overview`
`28 March 2025`	`1.3`	`Include flightId in the Notification Payload`
`20 June 2025`	`1.4`	`Added Scheduled Flight Notification`
`23 June 2025`	`1.5`	`Added Estimated and Confirmed On-Time Departure Notifications`
`23 September 2025`	`1.6`	`ACDM compliant payload`

2 Introduction

The SITA Advance Flight Delay API is a REST-based subscription service that provides real-time updates for delayed flights or potential delays for arrival flights impacted by delays at departure airports worldwide.

Users can:

Subscribe to receive real-time push notifications at an endpoint of their choice.

Delete subscriptions that they have previously created.

Advance Flight delay notifications can be requested by issuing a POST request with the relevant payload to:

Examples:
- https://sitaopen.api.aero/advanceflightdelay/v1/subscribe
- https://sitaopen-qa.api.aero/advanceflightdelay/v1/subscribe
- https://sitaopen.api.aero/advanceflightdelay/v1/unsubscribe
- https://sitaopen-qa.api.aero/advanceflightdelay/v1/unsubscribe

A user may subscribe for Advance Flight Delay notifications by specifying an airport.

Key points to note:

Delays at departure airports will be pushed as soon as they are available to the corresponding arrival airport.
If a flight is 15 minutes past its scheduled departure time without a departure status being sent, it will be considered delayed.
Once a delayed flight has departed, a notification will be sent to the subscribed arrival airport.
Retry attempts will be made 4 times, 2 minutes apart. If delivery remains unsuccessful after these retries, the notification will be dropped.

See 8 Appendix F - Advance Flight Delay Notification Payload Examples for examples of the Advance Flight Delay notification payload.

Example scenarios

Scenario 1: Subscribe to Advance Flight Delay notifications +

To subscribe to Advance Flight Delay for a specific airport, send a POST request with the following payload:

{
  "airportCode": "JFK",
  "callbackUrl": "https://myendpoint/delay.notification.handler"
}

In this example:
- airportCode specifies the airport for which delay notifications are required (e.g., JFK for John F. Kennedy International Airport).
- callbackUrl is the endpoint where notifications will be sent.

Scenario 2: Unsubscribe from Advance Flight Delay notifications +

To unsubscribe from flight delay notifications, send a DELETE request with the subscription ID in the payload:

{
  "subscriptionId": "12345678-1234-1234-1234-123456789012"
}

In this example:
- subscriptionId refers to the unique identifier of the subscription to be removed.

Scenario 3: Unsubscribe from Advance Flight Delay notifications +

Another option to unsubscribe from Advance Flight Delay notifications is to send a DELETE request with the airport code and the callback URL in the payload, those are the same values that were used to create the subscription:

{
  "airportCode": "JFK",
  "callbackUrl": "https://myendpoint/delay.notification.handler"
}

In this example:
- airportCode specifies the airport for which delay notifications were subscribed (e.g., JFK for John F. Kennedy International Airport).
- callbackUrl is the endpoint where notifications were sent.

Registration and API Sign Up

To access the APIs you will need a registration key, also known as an API key. These can be obtained by creating an account on https://www.developer.aero/ and registering your interest for access to the API.

3 Authentication

To access the APIs an OAuth access token must be supplied in an Authorization header in the request. To obtain an OAuth token a request must be sent to the https://sitaopen.api.aero/advanceflightdelay/oauth/token endpoint using the OAuth2 Client Credential flow. Use your API key as the client_id, and your consumer secret as the client_secret these should be base64 encoded in an Authorization header when sent to the OAuth endpoint.

Please note the OAuth tokens have an expiry of one hour after the token has been retrieved, after the token has expired you will need to re-issue a request to get a new token.

curl --location 'https://sitaopen.api.aero/advanceflightdelay/oauth/token' \--header 'Authorization: Basic YWJjZGVmZ2hpamtsbW5vcC5xcnN0dXY='

You should then see your OAuth token in the response.

"access_token": "eyJ0eXAiOiJKV1QiLCJhbGciOJIUzI1NiJ9.eyJyZWZyZXNoX3Rva2VuX2V4cGlyZXNfaW4iOiIzNTk5Iiwic3ViIjoic2l0YSIsImFwaV9cm9kdWN0X2xpc3QiOiJbRE9UUy1GbGlnaHQtQ29ubmVjdGlvbi1JbnRlcm5hbF0iLCJpc3MiOiJ1cm46XC9cL2FwaWdlZS1lZdlLUpXVC1wb2xpY3ktdGVzdCIsImFwaV9hY2Nlc3NfdG9rZW4iOiIweXlIZHduSUdtOGo5WlN6WWtuYTBsWG9ZNTFvIiwiYXBpX3JlZnJlc2hfdG9rZW4iOiJraHNlaXN2T3JwSHBUd2NuUVRHdXdBdVdicXNpamNQTyIsImFwaV9zY29wZSI6IiIsImF1ZCI6ImFwaWdlZS1hcGkiLCJleHAiOj3MzAyOTI3MzIsImFwcF9pZCI6IjIxYzI5NTgyLTIwZTktNDkwMS1hNjExLTVkM2UwM2QxNzFkYiIsImV4cGlyZXNfaW4iOiIzNTk5IiwiaWF0IjoxNzMwMjg5MTMyLCJqdGkiOiI3ZmEzNTU4Mi0xNDhmLTRiMmEtODYxMS0wNWI4NDg5YjFjYmMifQ.g_dFH-08DGADOX9HIk7wzX5edxXejVsnCen27A25TQ0"

Once an access token has been obtained, it can be placed in the Authorization HTTP header as a bearer token, for example:

curl --location 'https://sitaopen.api.aero/advanceflightdelay/v1/subscribe' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer "eyJ0eXAiOiJKV1QiLCJhbGciOJIUzI1NiJ9.eyJyZWZyZXNoX3Rva2VuX2V4cGlyZXNfaW4iOiIzNTk5Iiwic3ViIjoic2l0YSIsImFwaV9cm9kdWN0X2xpc3QiOiJbRE9UUy1GbGlnaHQtQ29ubmVjdGlvbi1JbnRlcm5hbF0iLCJpc3MiOiJ1cm46XC9cL2FwaWdlZS1lZdlLUpXVC1wb2xpY3ktdGVzdCIsImFwaV9hY2Nlc3NfdG9rZW4iOiIweXlIZHduSUdtOGo5WlN6WWtuYTBsWG9ZNTFvIiwiYXBpX3JlZnJlc2hfdG9rZW4iOiJraHNlaXN2T3JwSHBUd2NuUVRHdXdBdVdicXNpamNQTyIsImFwaV9zY29wZSI6IiIsImF1ZCI6ImFwaWdlZS1hcGkiLCJleHAiOj3MzAyOTI3MzIsImFwcF9pZCI6IjIxYzI5NTgyLTIwZTktNDkwMS1hNjExLTVkM2UwM2QxNzFkYiIsImV4cGlyZXNfaW4iOiIzNTk5IiwiaWF0IjoxNzMwMjg5MTMyLCJqdGkiOiI3ZmEzNTU4Mi0xNDhmLTRiMmEtODYxMS0wNWI4NDg5YjFjYmMifQ.g_dFH-08DGADOX9HIk7wzX5edxXejVsnCen27A25TQ0"
--data '{
  "airportCode": "JFK",
  "callbackUrl": "https://myendpoint/delay.notification.handler"
}'

4 Security

All incoming requests will be REST over HTTPS.
Users are authenticated using their API key.
Certain response payload elements will be filtered based on permissions associated with the x-apikey value used.
The API key used in the initial Advance Flight Delay REST call will be included as the response header 'X-apikey' in the pushed update message returned to the end user.

5 Error Response

Response fields

Path	Type	Description
`errors`	`Object`	Object that holds the error information
`errors.error[]`	`Array`	Array of errors
`errors.error[].code`	`Number`	API Internal Error Code
`errors.error[].description`	`String`	Error Description
`errors.error[].invalidParam`	`String`	Indicates the invalid query parameter

HTTP response

5 Rate Limiting

All incoming requests are subject to a rate limiting restriction. The following headers are included in HTTP responses:

Header	Description
`X-RateLimit-Limit`	The total number of requests allowed in the current time window
`X-RateLimit-Remaining`	The number of requests left for the current time window
`X-RateLimit-Policy`	The policy describing how many request per time window are allowed
`X-RateLimit-Reset`	The number of seconds remaining in the current time window. Header not displayed after rate limit has been exceeded
`retry-after`	The epoch timestamp at which the current rate limit window resets. Header only displayed after rate limit has been exceeded

6 Resources

This section describes the Advance Flight Delay API service.
Detailed API structure, example requests and responses, JSON schema for request (where appropriate) and responses, and error response codes and formats are included.

Advance Flight Delay V1

Subscribe to Advance Flight Delay

This resource enables users to subscribe to Advance Flight Delay notifications for arriving flight to an airport.

airportCode

Specifies the airport for which Advance Flight Delay notifications are required (e.g., JFK for John F. Kennedy International Airport).

callbackUrl

The endpoint where notifications will be sent.

POST /advanceflightdelay/v1/subscribe

Request headers

Name	Optional	Description
Content-Type	false	Content type of this request. Required value is 'application/json'
Authorization	false	Authorization header that contains the access token.

Request fields

Path	Type	Description
`airportCode`	`String`	3-character airport IATA code.
`callbackUrl`	`String`	The URL where the Advance Flight Delay notifications will be sent (HTTP/HTTPS).

Response fields

Path	Type	Description
`subscriptionId`	`String`	The unique identifier of the subscription

Curl request

$ curl 'https://developer.api.aero/api-catalog/advanceflightdelay/v1/subscribe' -i -X POST \
    -H 'Authorization: Bearer eyJkb2N1bWVudGF0aW9uIiwidG9rZW4ifQ...' \
    -H 'Content-Type: application/json' \
    -d '{
  "airportCode" : "JFK",
  "callbackUrl" : "https://example.com/callback"
}'

Request body

{
  "airportCode" : "JFK",
  "callbackUrl" : "https://example.com/callback"
}

HTTP response

When a flight delay occurs for a subscribed airport, a Advance Flight Delay notification message is sent to the user.

See 5 Appendix C - Push Notification Fields for a description of the fields in the push notification.

See 9 Appendix G - Advance Flight Delay HTTP Push Notification Example for an example of a raw HTTP push notification sent by Advance Flight Delay.

Unsubscribe from Advance Flight Delay

This resource provides the user with the ability to remove a advance flight delay subscription from the system.
This will result in the user receiving no further flight delay updates for the relevant airport.

subscriptionId

The unique identifier of the subscription to be removed. Optional if both airportCode and callbackUrl are present.

airportCode

Specifies the airport for which Advance Flight Delay notifications are sent (e.g., JFK for John F. Kennedy International Airport). Optional if subscriptionId is present.

callbackUrl

The endpoint where notifications are sent. Optional if subscriptionId is present.

DELETE /advanceflightdelay/v1/unsubscribe

Request headers

Name	Optional	Description
Content-Type	false	Content type of this request. Required value is 'application/json'
Authorization	false	Authorization header that contains the access token.

Request fields

Path	Type	Description
`airportCode`	`String`	3-character airport IATA code.
`callbackUrl`	`String`	The URL where the Advance Flight Delay notifications are being sent.
`subscriptionId`	`String`	The unique identifier of the subscription.

Curl request

$ curl 'https://developer.api.aero/api-catalog/advanceflightdelay/v1/unsubscribe' -i -X DELETE \
    -H 'Authorization: Bearer eyJkb2N1bWVudGF0aW9uIiwidG9rZW4ifQ...' \
    -H 'Content-Type: application/json' \
    -d '{
  "subscriptionId" : "12345678-1234-1234-1234-123456789012",
  "airportCode" : "JFK",
  "callbackUrl" : "https://example.com/callback"
}'

Request body

{
  "subscriptionId" : "12345678-1234-1234-1234-123456789012",
  "airportCode" : "JFK",
  "callbackUrl" : "https://example.com/callback"
}

HTTP response

Note: Provide either subscriptionId or (airportCode with callbackUrl), not both.

Example Subscribe to Advance Flight Delay request payloads

Subscribe request for advance flight delays arriving at Dublin Airport (DUB). The notification details will be sent to the provided 'callbackUrl'.

{
  "airportCode": "DUB",
  "callbackUrl": "https://myendpoint.delay.notification/callback"
}

Appendix B Unsubscribe from Advance Flight Delay Examples

Example Unsubscribe from Advance Flight Delay request payloads

Unsubscribe request from advance flight delays arriving at Dublin Airport (DUB). The following payloads are valid:

{
  "subscriptionId": "12345678-1234-1234-1234-123456789012"
}

{
  "airportCode": "DUB",
  "callbackUrl": "https://myendpoint.delay.notification/callback"
}

{
  "subscriptionId": "12345678-1234-1234-1234-123456789012",
  "airportCode": "DUB",
  "callbackUrl": "https://myendpoint.delay.notification/callback"
}

Appendix C Push Notification Fields

Field	Description
flightId	The unique identifier for the flight
airlineCode	The IATA code representing the airline
flightNumber	The unique number assigned to the flight
departureAirportCode	The IATA code of the departure airport
arrivalAirportCode	The IATA code of the arrival airport
flightStatus	The current status of the flight
averageFlightDuration	The average duration of the flight in minutes
scheduledFlightDuration	The scheduled duration of the flight in minutes
estimatedFlightDuration	The estimated duration of the flight in minutes
actualFlightDuration	The actual duration of the flight in minutes
departureDelay	The delay in departure time in minutes
arrivalDelay	The delay in arrival time in minutes
departureAdvance	The advance in departure time in minutes
arrivalAdvance	The advance in arrival time in minutes
delayType	The type of delay
delayReason	The reason for the delay
departure.sobt	Scheduled Off-Block Time
departure.stot	Scheduled Take-Off Time
departure.eobt	Estimated Off-Block Time
departure.etot	Estimated Take-Off Time
departure.aobt	Actual Off-Block Time
departure.atot	Actual Take-Off Time
arrival.sldt	Scheduled Landing Time
arrival.sibt	Scheduled In-Block Time
arrival.eldt	Estimated Landing Time
arrival.eibt	Estimated In-Block Time
arrival.aldt	Actual Landing Time
arrival.aibt	Actual In-Block Time

Appendix D Delay Types

Delay Type	Delay Reason
CONFIRMED_ON_TIME_DEPARTURE	Flight has departed on-time
CONFIRMED_ARRIVAL_DELAY	Confirmed delay based on actual times
CONFIRMED_EARLY_ARRIVAL	Flight arrived earlier than scheduled
CONFIRMED_RECOVERED_DELAY	Delay recovered, flight is now closer to schedule
ESTIMATED_ON_TIME_DEPARTURE	Flight is expected to depart on-time
ESTIMATED_ARRIVAL_DELAY	Estimated delay based on estimated times \| Estimated arrival delay due to actual departure being after the scheduled time
ESTIMATED_EARLY_ARRIVAL	Flight is expected to arrive earlier than scheduled
ESTIMATED_RECOVERED_DELAY	Delay recovered, flight is now closer to schedule
POTENTIAL_DEPARTURE_DELAY	Potential delay detected due to lack of departure status update
SCHEDULED	Flight Scheduled

Appendix E Flight Status Codes

Code	Description	Status Description
AD	Arrived-Diverted	Flight has arrived at gate at diversion airport
AP	Approach	Flight is approaching destination airport
AR	Arrived	Flight has arrived at destination airport
AT	See Agent	Indicator of a see flight agent
BC	Boarding Complete	Boarding process has completed
BD	Boarding	Flight is open for boarding
BO	Boarded	Boarding process has completed
CD	Baggage Delay	Indicator of possible baggage delay
CO	Closed	Gate has closed
CL	Closed	Gate has closed
CX	Cancelled	Flight has been cancelled
DE	Deleted	Flight has been deleted
DL	Delayed	Flight has been delayed
DP	Departed	Flight has departed gate/pushed back
DV	Diverted	Flight has been diverted to another location
EN	Enroute	Flight is enroute
EX	Expected	Flight expected time of departure/arrival
FB	First Bag Unloaded	First bag has been unloaded
FC	Final Call	Final call to gate
GC	Gate Closed	Gate has closed
GG	Go To Gate	Passengers call to gate
GT	Gate Time (Gate Time HH:MM can be found in gateInfo field)	Gate information will be available at specified time
IA	In Air	Flight is in-air/taken off
ID	In Air-Diverted	Flight has been diverted to another location while in-air
IR	In Range	Flight is within the operational range of the airport’s navigation and communication systems
LB	Last Bag Unloaded	Last bag has been unloaded
LD	Landed-Diverted	Flight has landed at diversion airport
LN	Landed	Flight has landed at destination airport
LR	Landed-Recovered	Flight from diversion airport has landed at original destination airport
OG	Landed (On Ground)	Flight has landed at destination airport
ON	On Time	Flight is on-time
TX	Taxiing	Aircraft is taxiing
PD	Possible Delay	Indicator of a possible flight delay
RA	Arrived-Recovered	Flight from diversion airport has arrived at gate at original destination airport
RE	In Air-Recovered	Flight from diversion airport to original destination airport has taken off
RG	Return To Gate	Flight has attempted to take-off but has turned back-around to the gate
SC	Scheduled	Flight scheduled time of departure/arrival
UN	Unknown	Flight status is unknown or unavailable
VN	TEST	Test flight in system
WX	SITA Advance Flight Delay API	Indicated SITA Advance Flight Delay API may have an impact of the flight operation

Appendix F Advance Flight Delay Notification Payload Examples

The following JSON payloads represent various types of flight delay notifications.
Each payload includes detailed information about the flight, such as the airline code, flight number, departure and arrival airport codes, flight status, and various durations (average, scheduled, estimated, and actual).
Additionally, they provide the delay in departure and arrival times, the type of delay, and the reason for the delay.
The departure and arrival fields contain nested objects with scheduled, estimated, and actual times for both departure and arrival.
These comprehensive payloads help in understanding the specifics of the delay and the flight’s overall status.

Example of a Confirmed Arrival Delay Notification Payload

{
  "flightId": "194384268",
  "airlineCode": "AA",
  "flightNumber": "1026",
  "departureAirportCode": "SDQ",
  "arrivalAirportCode": "MIA",
  "flightStatus": "AR",
  "averageFlightDuration": 145,
  "scheduledFlightDuration": 145,
  "estimatedFlightDuration": 145,
  "actualFlightDuration": 124,
  "departureDelay": 29,
  "arrivalDelay": 8,
  "delayType": "CONFIRMED_ARRIVAL_DELAY",
  "delayReason": "Confirmed delay based on actual times",
  "departure": {
    "sobt": "2025-09-23T07:00:00-04:00",
    "eobt": "2025-09-23T07:29:00-04:00",
    "aobt": "2025-09-23T07:29:00-04:00"
  },
  "arrival": {
    "sibt": "2025-09-23T09:25:00-04:00",
    "eibt": "2025-09-23T09:54:00-04:00",
    "aibt": "2025-09-23T09:33:00-04:00"
  }
}

Example of a Confirmed Early Arrival Notification Payload

{
  "flightId": "194387278",
  "airlineCode": "AA",
  "flightNumber": "3304",
  "departureAirportCode": "ORD",
  "arrivalAirportCode": "MIA",
  "flightStatus": "AR",
  "averageFlightDuration": 185,
  "scheduledFlightDuration": 185,
  "estimatedFlightDuration": 170,
  "actualFlightDuration": 148,
  "departureDelay": 3,
  "arrivalAdvance": 34,
  "delayType": "CONFIRMED_EARLY_ARRIVAL",
  "delayReason": "Flight arrived earlier than scheduled",
  "departure": {
    "sobt": "2025-09-23T06:09:00-05:00",
    "eobt": "2025-09-23T06:09:00-05:00",
    "aobt": "2025-09-23T06:12:00-05:00"
  },
  "arrival": {
    "sibt": "2025-09-23T10:14:00-04:00",
    "eibt": "2025-09-23T10:02:00-04:00",
    "aibt": "2025-09-23T09:40:00-04:00"
  }
}

Example of a Confirmed Recovered Delay Notification Payload

{
  "flightId": "194379317",
  "airlineCode": "FZ",
  "flightNumber": "897",
  "departureAirportCode": "DXB",
  "arrivalAirportCode": "MED",
  "flightStatus": "AR",
  "averageFlightDuration": 165,
  "scheduledFlightDuration": 165,
  "estimatedFlightDuration": 176,
  "actualFlightDuration": 150,
  "departureDelay": 15,
  "delayType": "CONFIRMED_RECOVERED_DELAY",
  "delayReason": "Delay recovered, flight is now closer to schedule",
  "departure": {
    "sobt": "2025-09-23T14:35:00+04:00",
    "eobt": "2025-09-23T14:50:00+04:00",
    "aobt": "2025-09-23T14:50:00+04:00"
  },
  "arrival": {
    "sibt": "2025-09-23T16:20:00+03:00",
    "eldt": "2025-09-23T16:36:00+03:00",
    "eibt": "2025-09-23T16:46:00+03:00",
    "aibt": "2025-09-23T16:20:00+03:00"
  }
}

Examples of an Estimated Arrival Delay Notification Payload

{
  "flightId": "194416625",
  "airlineCode": "XY",
  "flightNumber": "575",
  "departureAirportCode": "CAI",
  "arrivalAirportCode": "MED",
  "flightStatus": "IA",
  "averageFlightDuration": 110,
  "scheduledFlightDuration": 110,
  "estimatedFlightDuration": 98,
  "departureDelay": 21,
  "arrivalDelay": 9,
  "delayType": "ESTIMATED_ARRIVAL_DELAY",
  "delayReason": "Estimated delay based on estimated times",
  "departure": {
    "sobt": "2025-09-23T16:30:00+03:00",
    "eobt": "2025-09-23T16:30:00+03:00",
    "etot": "2025-09-23T16:42:00+03:00",
    "aobt": "2025-09-23T16:51:00+03:00",
    "atot": "2025-09-23T16:51:00+03:00"
  },
  "arrival": {
    "sibt": "2025-09-23T18:20:00+03:00",
    "eldt": "2025-09-23T18:19:00+03:00",
    "eibt": "2025-09-23T18:29:00+03:00"
  }
}

{
  "flightId": "194413949",
  "airlineCode": "F3",
  "flightNumber": "131",
  "departureAirportCode": "RUH",
  "arrivalAirportCode": "JED",
  "flightStatus": "IA",
  "averageFlightDuration": 105,
  "scheduledFlightDuration": 105,
  "estimatedFlightDuration": 105,
  "departureDelay": 15,
  "arrivalDelay": 15,
  "delayType": "ESTIMATED_ARRIVAL_DELAY",
  "delayReason": "Estimated arrival delay due to actual departure being after the scheduled time",
  "departure": {
    "sobt": "2025-09-23T16:25:00+03:00",
    "eobt": "2025-09-23T16:40:00+03:00",
    "etot": "2025-09-23T16:35:00+03:00",
    "aobt": "2025-09-23T16:40:00+03:00",
    "atot": "2025-09-23T16:40:00+03:00"
  },
  "arrival": {
    "sibt": "2025-09-23T18:10:00+03:00",
    "eldt": "2025-09-23T18:00:00+03:00",
    "eibt": "2025-09-23T18:25:00+03:00"
  }
}

Example of an Estimated Early Arrival Notification Payload

{
  "flightId": "194390891",
  "airlineCode": "AA",
  "flightNumber": "1498",
  "departureAirportCode": "MEX",
  "arrivalAirportCode": "MIA",
  "flightStatus": "IA",
  "averageFlightDuration": 206,
  "scheduledFlightDuration": 206,
  "estimatedFlightDuration": 173,
  "departureDelay": 5,
  "arrivalAdvance": 28,
  "delayType": "ESTIMATED_EARLY_ARRIVAL",
  "delayReason": "Flight is expected to arrive earlier than scheduled",
  "departure": {
    "sobt": "2025-09-23T05:35:00-06:00",
    "eobt": "2025-09-23T05:35:00-06:00",
    "aobt": "2025-09-23T05:40:00-06:00"
  },
  "arrival": {
    "sibt": "2025-09-23T11:01:00-04:00",
    "eibt": "2025-09-23T10:33:00-04:00"
  }
}

Example of an Estimated Recovered Delay Notification Payload

{
  "flightId": "195406321",
  "airlineCode": "R7",
  "flightNumber": "450",
  "departureAirportCode": "SJU",
  "arrivalAirportCode": "MIA",
  "flightStatus": "IA",
  "averageFlightDuration": 142,
  "scheduledFlightDuration": 142,
  "estimatedFlightDuration": 132,
  "departureDelay": 22,
  "arrivalDelay": 12,
  "delayType": "ESTIMATED_RECOVERED_DELAY",
  "delayReason": "Delay recovered, flight is now closer to schedule",
  "departure": {
    "sobt": "2025-09-23T09:15:00-04:00",
    "eobt": "2025-09-23T09:37:00-04:00",
    "aobt": "2025-09-23T09:37:00-04:00",
    "atot": "2025-09-23T09:37:00-04:00"
  },
  "arrival": {
    "sibt": "2025-09-23T11:37:00-04:00",
    "eldt": "2025-09-23T11:49:00-04:00"
  }
}

Example of a Potential Departure Delay Notification Payload

{
  "flightId": "194419586",
  "airlineCode": "SV",
  "flightNumber": "216",
  "departureAirportCode": "AMS",
  "arrivalAirportCode": "JED",
  "flightStatus": "SC",
  "averageFlightDuration": 350,
  "scheduledFlightDuration": 350,
  "delayType": "POTENTIAL_DEPARTURE_DELAY",
  "delayReason": "Potential delay detected due to lack of departure status update",
  "departure": {
    "sobt": "2025-09-23T15:55:00+02:00"
  },
  "arrival": {
    "sibt": "2025-09-23T22:45:00+03:00"
  }
}

Example of a Flight Scheduled Notification Payload

{
  "flightId": "194580918",
  "airlineCode": "SV",
  "flightNumber": "376",
  "departureAirportCode": "CMN",
  "arrivalAirportCode": "JED",
  "flightStatus": "SC",
  "averageFlightDuration": 370,
  "scheduledFlightDuration": 370,
  "delayType": "SCHEDULED",
  "delayReason": "Flight Scheduled",
  "departure": {
    "sobt": "2025-09-24T07:40:00+01:00",
  },
  "arrival": {
    "sibt": "2025-09-24T15:50:00+03:00",
  }
}

Example of an Estimated On-Time Departure Notification Payload

{
  "flightId": "194450242",
  "airlineCode": "AA",
  "flightNumber": "605",
  "departureAirportCode": "LGA",
  "arrivalAirportCode": "MIA",
  "flightStatus": "SC",
  "averageFlightDuration": 195,
  "scheduledFlightDuration": 195,
  "estimatedFlightDuration": 195,
  "delayType": "ESTIMATED_ON_TIME_DEPARTURE",
  "delayReason": "Flight is expected to depart on-time",
  "departure": {
    "sobt": "2025-09-23T13:01:00-04:00",
    "eobt": "2025-09-23T13:01:00-04:00",
    "etot": "2025-09-23T13:27:00-04:00"
  },
  "arrival": {
    "sibt": "2025-09-23T16:16:00-04:00",
    "eibt": "2025-09-23T16:16:00-04:00"
  }
}

Example of a Confirmed On-Time Departure Notification Payload

{
  "flightId": "194419593",
  "airlineCode": "SV",
  "flightNumber": "1471",
  "departureAirportCode": "RUH",
  "arrivalAirportCode": "MED",
  "flightStatus": "DP",
  "averageFlightDuration": 95,
  "scheduledFlightDuration": 95,
  "estimatedFlightDuration": 95,
  "delayType": "CONFIRMED_ON_TIME_DEPARTURE",
  "delayReason": "Flight has departed on-time",
  "departure": {
    "sobt": "2025-09-23T16:55:00+03:00",
    "eobt": "2025-09-23T16:55:00+03:00",
    "etot": "2025-09-23T17:05:00+03:00",
    "aobt": "2025-09-23T16:55:00+03:00"
  },
  "arrival": {
    "sibt": "2025-09-23T18:30:00+03:00",
    "eibt": "2025-09-23T18:30:00+03:00"
  }
}

Appendix G Advance Flight Delay HTTP Push Notification Example

This appendix provides an example of a raw HTTP push notification sent by Advance Flight Delay. The example demonstrates how the HTTP request is structured, including the headers and the JSON payload. This example is useful for developers implementing a notification handler.

SITA Advance Flight Delay Notification API1.0.0-SNAPSHOT

Overview

1 Revision History

2 Introduction

3 Authentication

4 Security

5 Error Response

5 Rate Limiting

6 Resources

Appendix B Unsubscribe from Advance Flight Delay Examples

Appendix C Push Notification Fields

Appendix D Delay Types

Appendix E Flight Status Codes

Appendix F Advance Flight Delay Notification Payload Examples

Appendix G Advance Flight Delay HTTP Push Notification Example

Contact Us

For subscription and sales queries, please contact:

For any technical queries and support, please contact:

About us

Overview

1 Revision History

2 Introduction

3 Authentication

4 Security

5 Error Response

5 Rate Limiting

6 Resources

Appendix A Subscribe to Advance Flight Delay Examples

Appendix B Unsubscribe from Advance Flight Delay Examples

Appendix C Push Notification Fields

Appendix D Delay Types

Appendix E Flight Status Codes

Appendix F Advance Flight Delay Notification Payload Examples

Appendix G Advance Flight Delay HTTP Push Notification Example

Contact Us

For subscription and sales queries, please contact:

For any technical queries and support, please contact:

About us