I am currently testing the NS1 Connect API for an enterprise-scale integration. I've noticed that the endpoints for listing teams and users do not seem to honor standard pagination parameters.
-
Does the API support limit and offset (or page and per_page) for the /account/teams and /account/users routes?
-
If not, how does IBM recommend handling accounts with 500+ users or teams to avoid large payload timeouts and high memory usage during the initial fetch?
-
Is there a plan to bring these endpoints in line with the pagination standards used in other IBM Cloud API handbooks?
#GeneralQuery(forthefreemiumusers)#TechnicalAssistance(forthefreemiumusers)#Technical------------------------------
Shobhit Kumar
------------------------------