Question about calls billing of the AirportBoards endpoint


#1

Hello,

We perform one request to the “AirportBoards” endpoint every 2 hours, with the intention to only use one API call per request. When I call up https://flightaware.com/commercial/flightxml/billing/activity/recent, I see that sometimes up to 4 calls are billed per request. I’d like to understand why this is the case, and how I can avoid to go over 1 call. The 2 types that I’m interested in are “enroute” and “scheduled”.

Currently we use the default “AirportBoards” request with no parameters except of “airport_code”

What parameters do I need to set to make sure that I only use 1 call per 2 hours?


#2

Are you making a call for each individually?


#3

Thanks for your answer.

We are making one call without any additional parameter beside “airport_code”. All 4 types are returned in the result. Is it possible to only query the 2 endpoints we need within one call, and keeping the count to 1?


#4

It’s buried in the forums here somewhere, but, yes, each HTTP call to the AirportBoard API counts as one billable query, as long as you don’t get more than 15 flights in each of the enroute, scheduled, etc. results.


#5

Hello ottergoose, thanks for your reply. Do you mean that as soon i receive more than 15 flights with all 4 types counted together, it will count more than one?

Online_JSON_Viewer

This response with 10 flights per type was billed with 3 calls.

I guess what i need to to is splitting the calls into one for enroute and one for schedule, and limiting both to 15. This should make sure they only count as one each.


#6

Arrivals, departures, enroute, and scheduled can each contain up to 15 flights (that’d be up to 60 flights between the four) and the API call should count as 1 billable query.


#7

Hmm, this is not how i experienced it. I agree with you that it should behave like that, but from what i see it isn’t.

40 flights got billed for 3 calls, which is in the (3 x 15) range. I also experienced getting billed for 4 calls with a single AirportBoards response. Back then i had no parameter set for howMany, so it was default (15).


#8

I am seeing now that the majority of the results are 1 query. Were you able to resolve the issue?


#9

@cbw I am still trying to understand why not every request is billed with 1. We make the exact same request every 2 hours, and if @ottergoose was right with his assumption, this should always just cost 1 call.

The only parameter changed since the beginning of this topic is “howMany”, which is now set to 11.

Do you maybe have more insight to the API connection details from our IP 165.227.103.209? How does it explain that sometimes it costs 2 calls?


#10

FWIW, my application uses a healthy volume of FXML3 airport board calls - I just did a quick audit to verify my requests jive with FlightAware’s reporting (which I should have done before, but hadn’t), and it looks pretty solid; in a time period with over 10,000 requests, the count discrepancy was just 1 - an error rate of less than 1/10 of 1%.

In other words, I’m not experiencing the same issue with my FXML3 AirportBoard queries as you are - will be interesting to see what the issue is.


#11

Let me have someone check it out. Realistically, the howMany shouldnt matter as long as it is under 15. Blank/Deafult would provide that limit


#12

@cbw Thanks for this!


#13

After looking at the data. We are seeing 2 calls made that are hitting 2 different servers. These calls are made at the same time but would start and end with the same server. Therefore, if we see 2 calls hitting 2 different servers, that would indicate that they are both unique calls made, and therefore, you are seeing the 2 calls charged.


#14

@cbw Thanks for you detailed answer. I will make sure that only 1 call is made at the time on our side. The script is very simple and executed via cronjob, so I wonder what the issue could be. Thanks for clearing things up for me!

@ottergoose Also thanks to you for the participation in this. It’s very clear now that the issue is somewhere on our side.