:0 at the end of fa_ident sometimes

FlightAware AeroAPI
1

Why does the fa_ident sometimes contain a :0 at the end, but sometimes not?

On the AirlineFlightSchedules, I found ASA1331-1563770742-airline-0046:0 but when using AirportBoards, the flight is found under ASA1331-1563770742-airline-0046.

And there are plenty more examples of this. Is there a reason for this?

2

I’ve had to manually filter out “:X” to prevent that from being an issue; there’s at least one other thread about it here, something they’ll need to fix on their end, eventually.

3

Here’s the old thread with this bug: FAFlightID received by push does not exactly match what was registered - #3 by StrideWebjet1

4

Thanks for that link. Looks like they never addressed the issue. But I did the same type of filter, and I guess I’ll just have to live with it.

5

That extra value should be ignored. Looks like we missed that case when cleaning up the value. If you do spot any other endpoints where the : is present please let us know and we’ll get it fixed.