Welcome to the Panopto Community

Please note: All new registrants to the Panopto Community Forum must be approved by a forum moderator or admin. As such, if you navigate to a feature that is members-only, you may receive an error page if your registration has not yet been approved. We apologize for any inconvenience and are approving new members as quickly as possible.

GetSessionDetailedUsage API Returns Both Valid and Invalid Users

Lily LiLily Li Tyro
in API

Hi Team,

Good morning. We are using GetSessionDetailedUsage API to get the list of user IDs for the session. It turns out that the userIDs returned from GetSessionDetailedUsage API includes both valid users and invalid users. For those invalid users, the account does not exist in Panapto if doing the search on it, and will return invalid userID if run GetuserbyID API on it. We are wondering why invalid users returned (probably those are former users) and whether GetSessionDetailedUsage API can be updated to only return the valid users so that we don't need to filter invalid users out from our side each time using GetuserbyID API with more program/resources involved as there are about 1/3 invalid users out of total users returned.

Thanks,

Lily

Answers

  • Adis HrnjicaAdis Hrnjica Whiz Kid

    Hi Lily,

    You are correct that currently we return both valid and invalid users. I'll create internal item to try to fix this in the future.

    In the meantime we could potentially upgrade your workflow with below steps:

    (1) Call GetSessionDetailedUsage, dedupe the returned UserId values

    (2) Send them in batches to GetUsers

    (3) Keep only the GUIDs that come back. Any GUIDs that cause an exception or are not returned are no longer valid and can be dropped. Chunk the list to avoid large payloads and catch/ignore the “invalid userId” errors.

    I hope this helps.

    Thanks,

    Adis

  • Lily LiLily Li Tyro

    Hi Adis,

    Thanks for the update. This is what our end user do from their program. But as we have a big amount of IDs, these steps consumes additional resources and time consuming. It would be great if this issue can be fixed from your API side directly. Please update us once it's fixed.

    Many thanks,

    Lily

Sign In or Register to comment.