Pagination/limit query for mods route

[ThatTonybo]

Making a request to https://mods.vintagestory.at/api/mods seems to have no way to limit the response amount, and with currently >5700 mods in one request, makes it a bit hard to work with. I tried to inspect the ModDB website but couldn't figure out how the lazy loading is implemented properly.

Assuming that there is some form of cursor pagination already implemented, but is there any documentation for this or any sort of query limiting? Would love to request say 50 mods at a time.

[SaculRennorb]

Pagination is not currently available via the api. The v1 api you are referring to is considered legacy at this point and will not receive further updates, but the equivalent list endpoint in v2 would probably get pagination.
Of note however is that the second version would likely have a different shape in general, as i do not think the current version of the list endpoint makes much sense as it exists now. There is close to no difference to the data returned by it compared to requesting individual information, and the information that is not returned ins completely arbitrary.

[ThatTonybo]

Gotcha! Is the v2 list route already available or still a work in progress?

In the meantime, I'll probably just request the v1 mods list once and paginate it myself.

[SaculRennorb]

No, all the available v2 routes are documented and the list route does not (yet) exist.

I would also recommend to cache the current endpoint locally for 30-ish minutes, and just locally paginate it as desired.
This will also give you way shorter response times should you want to do any kind of searching of the data, and the data should have negligible storage requirements compared to even a single image.

[ThatTonybo]

Yup, sounds like that'll be my plan going forward until the v2 routes mature a bit more. Much appreciated!