/flights/search/count always returns 400

I’m trying to get a count of airborne aircraft within a region and the query always returns {"count":400}.

The query is:

curl -X GET "https://aeroapi.flightaware.com/aeroapi/flights/search/count?query=-latlong%20%22-43.6345972634%20113.338953078%20-10.6681857235%20153.569469029%22" -H "Accept: application/json; charset=UTF-8" -H "x-apikey: <My API key>"

This link shows the extent of the bounding box: bbox finder. (NOTE: identical coordinates to the curl query.)

Checking internally. I reproed in the US as well as your box provided. If I had a smaller box, it returned what appeared to be a correct count.

I have raised a ticket to our AeroAPI Team. It does not appear that the ticket has been prioritized at this time, but will follow up when I see an update on the ticket.

Thank you.

In the meantime - how do I go about getting a credit on my account? I shouldn’t have to pay for an API that isn’t able to provide the information I need.

The standard account is subject to a minimum charge, in this case it will be prorated to reflect your sign up date. Should queries go over this amount, we will look into credits for the search/count queries. Currently I see about 17 queries to that particular endpoint.

I’m sorry but that doesn’t make sense. I’m not going to exceed the minimum charge because your endpoint is giving the wrong data, hence I’m not making requests.

When that endpoint is working I’ll be scheduling a task to hit it every 20 minutes.

Sooooo two-and-a-half weeks later and this endpoint is still giving the wrong answer.

Is there an ETA for this fix?

It is being worked, Ill ask the group what an ETA looks like.

Still awaiting a reply internally on timing.

A fix was released (V4.9.1) to lift the 400 restriction on 12/15/2021. We appreciate the feedback, and apologize for the inconvenience.

Thanks for the update Tammy.

I have a few points of feedback for FlightAware:

  • I’m really unimpressed by the response to my request for a credit. I signed up in November and haven’t yet been able to use FlightAware due to this issue, but you’ve been taking my $100 on time? That is not cool!
  • If there is a hard-coded restriction that information needs to be included in the documentation.
  • If the true value cannot be returned (e.g. due to a restriction) DO NOT RETURN A VALID VALUE. Instead return -1 or something else.
    • The documentation should state when -1 will be returned.

Your resourceful feedback and patience is truly appreciated. We will DM you to make sure you are taken care of.

1 Like