AeroAPI v2 - no results from AirlineFlightSchedules API call

FlightAware AeroAPI
1

I’m getting no results (data: ) for an API call today (10th May 2023) to ‘AirlineFlightSchedules’ endpoint;

http://{user_name}:{api_key}@flightxml.flightaware.com/json/FlightXML2/AirlineFlightSchedules?startDate=1683642601&endDate=1683728999&origin=YPLC&howMany=30&offset=0

This has been working for the past 2 years with no issues. If I go to the FlightAware website and type in the airport code I can see that there are departing flights scheduled for this date and period.
Note: the same API call for departures (as below) works fine and returns the expected results;

http://{user_name}:{api_key}@flightxml.flightaware.com/json/FlightXML2/AirlineFlightSchedules?startDate=1683642601&endDate=1683728999&destination=YPLC&howMany=30&offset=0

Note: I have tried with howMany=15 also and several other variation of the API call but still no results.

Please help!

2

we are using airlineflightschedules endpoint to get the status of the flight and getting no response, is there a known issue with the api ? any one working on it ? any eta ?

3

I was able to reproduce the issue. It appears to be an issue with the 9th specifically. I have asked the team to look into it. Not sure why it is not effecting the destination. If I choose the 10th, it returned data as would be expected with YPLC as the origin.

4

What specific queries were you using?

5

yes the issue is only with the todays flights, we are able to get a response back fro future flights. can you help resolve this please ?

we have a custom code in our app which make a call to your api end point, the code looks like below and calles airlineflightschedules endpoint with given parameters. this has been working fine for ages and some how recently we started facing problems every now and then. Today it is not giving any reponse for flight schediuled today

foo.get_scheduled_flights_for_departure(airline_icao: “AAL”, flight_number: “1148”, scheduled_departure: DateTime.now, departure_airport_icao: “DFW”, timezone: “CST”)

6

This should be resolved now. For both examples pulling recent historical schedules should be working again. It looks like some incomplete schedule data was in system and causing the unexpected result, it’s been removed.