List apps

client.apps.list() returns a page of apps (cursor-style pagination). Choose an approach below based on how much control you need over paging.

One page at a time

Use this when you build UI with Next/Previous, tables, or APIs that expose one page per request. You call list() for each screen, read page.data, and pass startingAfter / starting_after when hasMore / has_more is true.

list-page.js

// MY_APP_JSON =// { ... }

const page = await client.apps.list({

limit: 10, // max apps per page (1–100)

sortBy: "NEWEST", // other options: "OLDEST", "MOST_ACTIVE"

collaborating: false, // true = include apps shared with you from other namespaces

});

// Should return: {// { ... }

console.log(page.data);

console.log(page.hasMore, page.nextPageCursor);

if (page.hasMore) {

const nextPage = await client.apps.list({

limit: 10,

startingAfter: page.nextPageCursor,

});

console.log(nextPage.data);

}

Collect a bounded set

Use this when you only need up to N apps and do not want to write the paging loop yourself. In JavaScript, chain autoPagingToArray({ limit: N }) on list() — the SDK fetches pages until it reaches your cap or runs out of apps. In Python, use Stream every app below and stop after N items if you need a cap.

list-auto-paging.js

const firstFiveApps = await client.apps
  .list({ limit: 2, sortBy: "OLDEST", collaborating: false })
  .autoPagingToArray({ limit: 5 }); // max total apps to collect across pages
// Should return: [ MY_APP_JSON, ... ]
console.log(firstFiveApps);

Stream every app

Use this for scripts, exports, or sync jobs when you want to walk the full list. The SDK keeps requesting pages until there are no more results. In JavaScript use for await; in Python, iterate the object returned by list().

list-stream.js

for await (const app of client.apps.list({
  limit: 25,
  sortBy: "MOST_ACTIVE",
  collaborating: false,
})) {
  // Should log: MY_APP_JSON
  console.log(app.id, app.name, app.url);
}

Source: stackmachine/sdks examples.