Endpoints

  • GET /users - list users
  • GET /users/{userId} - get details of a user by user id

User Object

  • id (string) - the unique identifier of the user
  • email (string) - the user's email address
  • groupsUrl (string) - URL to list user's groups from the API
  • role (string) - the user's role (one of learner, author, reporter, or admin)
  • firstName (string) - the user's first name
  • lastName (string) - the user's last name
  • learnerReportUrl (string) - URL to fetch the user's learner report from the API
  • url (string) - URL to fetch user's details from the API

Retrieving a List of Users

GET /users

Parameters

  • limit (integer, optional) - the maximum number of results to return in a single response (defaults to 50)
  • email (string, optional) - if provided, only return users with this email address

Example Response

{ 
"users": [
{
"id": "example-user-id-1",
"email": "foo@example.com",
"role": "learner",
"firstName": "Example First Name 1",
"lastName": "Example Last Name 1",
"learnerReportUrl": "https://api.rise.com/reports/learners/example-user-id-1",
"url": "https://api.rise.com/users/example-user-id-1"
}, ...
],
"nextUrl": "https://url-for-next-page-of-results"
}

Retrieving Specific User Details

GET /users/{userId}

Parameters

  • No parameters

Example Response

{ 
"id": "example-user-id",
"email": "example@example.com",
"role": "learner",
"firstName": "Example First Name",
"lastName": "Example Last Name",
"learnerReportUrl": "https://api.rise.com/reports/learners/example-user-id",
"url": "https://api.rise.com/users/example-user-id"
}

Endpoint-specific Error Codes

  • user_not_found - cannot retrieve user because user does not exist
Did this answer your question?