totalResults in pagination

For the listResponse endpoints of scim, for the totalResults property, does it include already fetched records (when startIndex > 1), or is it the total results from the start index? (totalResults = realTotalResults - startIndex - 1)
The specifications aren’t very clear on this, and we suspect not all IDPs understood the specification the same way.

Does someone have experience with this one?

Hi Doron,

totalResults will be the number of users on the SCIM server.
itemsPerPage will be the number of accounts returned in the Resources array
startIndex for Okta can either always be 1 or set it to the startIndex in the query param SCIM receives from Okta.

In my testing Okta will base the number of queries made off of the totalResults value returned in the very first request Okta makes /Users?startIndex=1&count=100
From this point on Okta will keep making requests count set to 100 incrementing startIndex by a 100 each time (1, 101, 201, …).

Hope that helps.

1 Like

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.