Hi,
I’m relatively new to eve and super new to the eve API.
I was looking around in the API explorer and found the Get wallet transactions endpoint.
It gets wallet transactions, I assume like the Transactions tab in the in-game wallet.
The Question I have is regarding to the optional filter field from_id. It provides a filter to only show transactions happened before the one referenced by this id.
why would this be useful?
like let’s assume I use the data from this endpoint to calculate the average buy price, wouldn’t I want to to have a filter for after the specified ID? Like I took all ready all earlier transactions into account and only want newer ones now?
I probably miss something, and I just want to know what 
Hey and welcome!
The from_idparameter is for paging. Each request returns at most 2.500 entries.
The first request returns the latest entries. If it has 2.500 entries, you can assume there are more pages. Then you can get the previous page making a request with from_id set to the lowest ID. And so on until you get a page that has less then 2.500 entries, which is the last page.
I just double checked and it seams that the wallet endpoint currently does not mention the 2.500 entries limit, which I think is a bug. The endpoint also has a 30 days limit, so you won’t get any entries which are older.
thx for the welcome and your answer.
why is this approach is is used instead of the pagefilter / X-Pages response like in example by List orders in a region?
I don’t know for sure, but you find many different approaches on paging in ESI. My guess is that has historical reasons, i.e. whatever the devs decided as the right approach at the time.
Case in point: The newest endpoint (corporation project) uses a brand new approach to paging.
think i read somewhere they are revamping the ESI anyway, changing how everything works with it.
Indeed. There already is a brand new version of ESI based on openAPI 3.x specs (previous was openAPI 2.0 / Swagger). This is now extended/changed by adding new versions.