Create TeamAdd Your APIDocs
Log In
Sign Up
Rapid account: Squawk7000

Squawk7000 / squawk7000

    No Published APIs
    This user has not published any APIs yet

    Discussions

    32
    Title
    		Created at (Click to sort ascending)
    A
    3
    		 Dear anmaria, You're looking for the date in future. Information for the future dates is based on schedules information and it looks like IX 540 is not reported in schedules anymore. I cross-checked on other web-sites and could not find confirmation that this flight is planned for January 2021. It hasn't been flying since May 8, 2020. It could be that this flight is just cancelled in general. 금 4:53 23/10/20
    A
    3
    		 Dear anmaria, You're looking for the date in future. Information for the future dates is based on schedules information and it looks like IX 540 is not reported in schedules anymore. I cross-checked on other web-sites and could not find confirmation that this flight is planned for January 2021. It hasn't been flying since May 8, 2020. It could be that this flight is just cancelled in general. 금 4:53 23/10/20
    A
    1
    		 Hi ttevik, Thanks for your request. Without a specific example it would very hard to say what is wrong with your request. But you can check if that's the problem you're facing: https://rapidapi.com/squawk7000/api/aerodatabox/discussions?issueId=13111&issueTitle=404-error It's a known problem with this endpoint: RapidAPI keeps generating wrong URL in code snippet (while internally using correct one). If you just copy-paste it from dashboard, it won't work. You have to put colons back. 화 2:20 29/9/20
    A
    2
    		 Hi! This is because flight data for NTAA wasn't covered by our API. Our API doesn't have world-wide coverage unfortunately as we warned in the description. For your convenience, I have added information for NTAA with scheduled data, but data with actual flight movements will unfortunately remain unavailable for now. 월 1:27 21/9/20
    A
    1
    		 Hi! It seems "number" parameter wasn't properly listed by us in API configuration in RapidAPI platform as allowed value. That's why it wasn't coming through. Now it's fixed. If you try now it should work :) 월 1:24 21/9/20
    A
    3
    		 Hi DarraghF, Sorry for a long reply. There was no notification about your response and I have just accidentally seen your message. We actually do have a mapping rule for few airlines (based on flight number range) when it's being operated by a different carrier. If you try searching by call-sign RPA4400, you should actually get AA4400 in the response. There is relatively good coverage for call-sign and reg data for flights operating from and to the USA, so many examples like this should be working. 월 7:27 7/9/20