Is there documentation for the new API?

Discussion in 'Other technical not related to ADSBx Feeding' started by XM192, May 29, 2019.

  1. XM192

    XM192 New Member

    Hello,

    I'm trying to move my Mac App to use the new API that requires a key. The data that comes back looks different, is there anything to document what the new values are? I'm not seeing Species in the new data which my App was taking to mean it probably isn't interesting enough to display.

    Thanks, Rob.
     
  2. XM192

    XM192 New Member

    After spending a bit of time on it it seems like the API is very similar except that "acList" is now "ac" and most of the keys are lower case.

    I used to rely on the "Id" field to find the aircraft so I know if I'm adding or updating but I don't see an equivalent or the other fields I used for "Mdl", "Op", "Engines", "Year" and "Species".
     
  3. James

    James Guest

    Just more sane format. Trying to keep it only to positional data, added a few fields that are database look ups that I regret upon request.

    fields should be self explanatory for the most part
     
  4. XM192

    XM192 New Member

    Thanks for the work on the API James.

    Is there a way to get the Species, Manufacturer, Model and Operator?

    I use Species to filter out ground vehicles and towers. I can get a type code like SPIT but that could refer to any of about 25 variants, likewise HAWK, EUFI and A332 (Voyager KC2 and KC3) could be a one of several.

    If you need to keep the response size down maybe this could be a secondary request, then we could cache that information locally against an ICAO and only refresh the information if it's older than a week or so.
     
  5. James

    James Guest

    That's all database look ups. So if we had a database I guess it's possible.