It would be really helpful to have the UUID and other user identifier fields returned in the courses/:id/users endpoint. This would better align the data being passed from LTI (uuid for the user_id) to build tighter LTI plus REST API integrations. Today we'd have to make the courses/:id/users call to gather the roster and then make individual /users calls for each user to get the UUID to map back to the LTI user.
If this were available, an external system can receive a single LTI launch to get the course ID (course UUID, and make the courses/:id/users call to gather all the other user's UUIDs to have the full roster without having to wait on LTI launches or making individual /users API calls to gather the UUIDs.
|Product Version (if applicable):|