If you use the /vx/ instead of the /latest/ they wont break on you like that. However if an endpoint gets too old it will start returning deprecated headers with the responses. Can keep an eye on the changelog to have an idea of what to expect.
EDIT: Oh wait you were talking about the order of the keys, im not sure that is guaranteed, probably be better of with like an array of objects like the response is?
Thanks! The changelog itself answers the questions I asked. You have also pointed me in the right direction to fix my code. I’m going to change my app to get the keys by name instead of their position in the array. It seems that the position is something that is subject to change. For example; When I first started this, I saw that type ID was the first key in an object and just assumed that would always be true, so I made an array and proceeded to grab the type ID from  in the array. Now I will just iterate through the array to find where the type ID is store currently.
If you aren’t doing anything special with the responses, why not just save the JSON response and use that directly vs iterating thru and making your own?
I think that would work up to a point, for things like system and item id’s but once I start using those values to find things like “system kills” which is updated every hour, or market prices which I assume are regularly updated, I need to get the most recent data.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.