All new and updated gate information can be made available to external customers who require it, via a subscription to a Kafka topic.

These events will be available in two forms: Public facing and Operations facing.

A notification will only take place if the flight has a status code and a valid Gate Number, which is usually set 50 minutes before the scheduled departure time.

A notification will take place regardless of if the flight has a status code.

Only Stand and Gate updates for departures will be sent.

Status codes are as follows:

('P', 'Pending')

('I', 'Gate Open')

('B', 'Boarding')

('F', 'Final Call')

('E', 'End Boarding')

('N', 'Gate Deallocated')

('C', 'Closed')

Statuses of N (deallocated) means that if there is a forced delay on the flight - these will still be sent through but with no gate number (empty string to be sent)

Fields that are required are as follows:

Airport:______________________________________________________________________________________________________________String

FlightDate:______________________________________________________________________String in UTC date format yyyy-mm-ddTHH:MM:SSZ

FlightNumber:_________________________________________________________________________________________________________String

GateAllocationDate:_______________________________________________________________String in UTC date format yyyy-mm-ddTHH:MM:SSZ

GateNumber:_________________________________________________________________________________________________________String

GateStatus:​​__________________________________________________________________________________________________________String

GateStatusCode:​______________________________________________________________________________________________________String

StandCode:__________________________________________________________________________________________________________String

Terminal:____________________________________________________________________________________________________________String

Example Message (payload):

Each integration will have a Topic created for that specific use case. All communications to the Kafka topics will be TLS via Certificate Auth and with IP Whitelisting.

Our SLA’s for this service are as follows:

Availability/Limited Resilience (Target 93.54% - Restoration 48 hrs)

• Manual failover or system rebuild

• Maximum data loss 60 hours

1.0.0 Initial Release