Attacks Key consistency

So I am creating a CLI app for myself to track attacks during a chain. When I request my attacks from https://www.torn.com/api.html I seem to get a full list of the last N number of attacks and the keys are consistent, yet when I am requesting via my http client they just come back all over the place and not in the same quantity?

is this a quirk of Torn? Theres obviously no pagination I am missing from this API right?

Iv have tested this and see what you mean

the HTTP listing is in reverse order for some reason, the lastest attacks are at the top

but when downloaded the lastest attacks are at the bottom

iv no idea why this is

The API throws an object which is not supposed to be ordered.

I'm not sure about the other languages but in python the equivalent is a dictionary which wouldn't have the fancy hash lookup if ordered.

But for the number of attacks it should be 100 (sometimes less if you enter from and to timestamps).

Calling attacks detailed will give you the last 100.
Calling just attacks gives the last 1000.
Attack ids are unique and can be used for de duplication before inserting into a database. Additionally attacks and revives can be ordered by these ids or by the time stamp inside the payload.