Add Your API
Add Your API
AeroDataBox / aerodatabox
Enthusiast-driven aviation and flight data API for a small travel or aviation application.
Hi! `Movement` stands for 'Arrival or Departure' and is essentially the same as neighboring `Arrival` or `Departure` properties. However, It can only be either `Movement` object or pair of `Arrival` and `Departure` object at any moment of time. Presence of either depends on `includeLeg` parameter of FIDS API call. When set to `true`, for all departures from this airport arrival information is also included, and for all arrivals - departure information. This way, each flight object contains both movement items. To distingiush which is arrival part and which is departure, corresponding `Arrival` and `Departure` properties are populated and `Movement` is removed. When it is set to `false`, all departures only contain departure information and all arrivals - arrival information. Therefore, only one movement item is present within each flight object. Consequently, no need for distinguishment. That's why only `Movement` is populated and `Arrival` and `Departure` are removed. Whether this `Movement` is arrival or departure is obvious from the location of the hosting flight object inside the whole response (it's either inside `Departures` or `Arrivals` collection). In other words, `Movement` is used whenever it's obvious from the context whether the movement is arrival or departure. In other cases more clear `Arrival` and `Departures` are used.
Since autocomplete is essentially a dynamic search, I think you can implement autocomplete using this endpoint
To everyone who might be affected: Apparently, RapidAPI rate limiting mechanisms inject HTTP response headers with names derived from corresponding pricing plan items' titles with disallowed characters transpired (against RFC7230). Incidentally, the recent pricing plan item we added contained "/" in the title. Obviously, this was done so without any awareness of the existence of this problem. We have already informed RapidAPI about the problem and they confirmed the issue is passed to R&D department. You might be affected by the issue, if: - you subscribed to any pricing plan between October 27, 2021 and November 2, 2021; and - programming language or framework you're using in your app enforces strict HTTP response header validation. As a workaround, we have updated pricing plans so that there are no potentially hazardous characters in their titles, but the issue won't be resolved for you right away. You have to: - re-subscribe to your pricing plan again (caution: if it is a paid plan, RapidAPI will charge you full month price again: you will have to drop them a message to email@example.com to request a refund; after that they will contact us, and we will approve the refund); or - disable strict validation of headers in your application; or - wait until RapidAPI fixes the issue (may last).
Hello again, We have now introduced Flight Subscription / PUSH API which may allow what you've been looking for earlier. You can read more about this new feature in our recent [news post](https://www.aerodatabox.com/news#h.e4ikhorrumdi).
Hi there! Thank you for the suggestion. I assume we are talking about the FIDS and flights endpoint, right? This is good idea. It's not as strait-forward to implement as it seems (we cannot just rely on IATA codes in flight numbers, as they are non-unique across the world for regional airlines operating in different parts of the globe), that's why it hasn't been done so far. However, there were some developments recently for the advanced airline mapping in our code-base. So, we can probably re-use it for flights part of the API. I'll list this suggestion for implementation.
It seems like this issue is somehow related to the new security feature of the RapidAPI which is standing between you and our API. It's supposed to provide additional validation of input parameters for endpoints. However, it looks like it's not working properly and takes correct parameters as wrong ones. We have switched it off for now, and going to report to RapidAPI about it. Please verify if everything works well on your side.