- Posts: 4
- Thank you received: 0
- Home>
- Forum>
- Support>
- Application Programming Interface>
- /tracks - Incorrect flight data returned
/tracks - Incorrect flight data returned
1 year 4 months ago #2456
by Akman
/tracks - Incorrect flight data returned was created by Akman
Hi all,
I've noticed the API has had a higher runtime as of late - thank you for the team for your continued support of this app.
I've lately noticed that the response returned from the GET /tracks is incorrect. The response contains details of what appears to be a different flight, despite the icao in the response matching the icao of the request. I cannot provide a screenshot right now, but will aim to do so later on if requested.
Thank you
I've noticed the API has had a higher runtime as of late - thank you for the team for your continued support of this app.
I've lately noticed that the response returned from the GET /tracks is incorrect. The response contains details of what appears to be a different flight, despite the icao in the response matching the icao of the request. I cannot provide a screenshot right now, but will aim to do so later on if requested.
Thank you
- strohmeier
- Away
- Administrator
-
Less
More
- Posts: 393
- Thank you received: 93
1 year 4 months ago #2475
by strohmeier
Replied by strohmeier on topic /tracks - Incorrect flight data returned
Indeed, that's why tracks is marked experimental in the documentation.
1 year 4 months ago #2485
by Akman
Replied by Akman on topic /tracks - Incorrect flight data returned
Yep, I read that before I posted.
Having said that, the tracks endpoint was working beautifully for the past ~3 months since I've been using. Because the endpoint is live and not down, I wanted to let you know about this issue as it may be less prone to automatic detection, and also to notify other users who may be using it so that they can work out an alternative for their apps.
No ETA expected and no request for it fixed, just a heads up mate.
Having said that, the tracks endpoint was working beautifully for the past ~3 months since I've been using. Because the endpoint is live and not down, I wanted to let you know about this issue as it may be less prone to automatic detection, and also to notify other users who may be using it so that they can work out an alternative for their apps.
No ETA expected and no request for it fixed, just a heads up mate.
