Hello @jibla. As you pointed out, Mastodon returns information related to pagination including the next minId in the HTTP Link header, and Masto.js is currently not offering a API for directly referring response headers.

However, we instead offer a higher level abstraction. All methods named list() actually returns an object that we call Paginator that can not only behave like a Promise, but also as a AsyncIterator.

Here's a basic example that favourite all posts on your home feed by using for-await-of syntax:

for await (const statuses of masto.v1.timelines.home.list()) {
  for (const status of statuses) {
    await masto.v1.statuses.$select(status.id).favourite();
  }
}

or if you want to fetch individual pages, you can use next()

const timeline = masto.v1.timelines.home.list();

const page1 = await timeline.next() // { done: false, value: [post, post, post...] } 
const page2 = await timeline.next();
const page3 = await timeline.next();

at the same time, you can fetch the first page by await

const timeline = await masto.v1.timelines.home.list();
//               ^^^^^
//               It now behaves like a Promise because we used `await`.
//               This is a synonym for `(await timelines.home.list().next()).value`

Therefore I believe we don't need to expose any HTTP information because you can encapsulate concrete implementation by using the Paginator API.

TSDoc comment for the limit property mentions about Link header but this is because we copy-and-pasted all descriptions from the Mastodon docs, which should be improved in the future.

I hope this helps