According to the documentation, offset is also not implemented. But even if it is implemented, this is another example where ISC APIs are not adhering to its own set standards meaning the clients would need to spend additional time to overwrite the code they use to paginate over objects for this specific type.
I think that instead of (or at least in addition to) suggesting workarounds to functionality incompleteness it would be nice if you could tell the engineering team that they have missed adding some important parts of the list objects API (count, offset, or even showing the list of access profile ids in the get and list source-apps APIs, just like it it shown in the patch source-app API regardless of which patch operations you use)
Or is this related to my question (gentle reminder here: A Smoother Development Experience: Introducing Our New API Versioning Strategy! - #38 by angelo_mekenkamp) where you said in mid September 2024 that the engineering team related to application APIs is not going to make anymore changes to these APIs, just because it was almost 2025 already?
Kind regards,
Angelo