Hub 2.0 Help

Get All User Details of a User

Request

GET /users/{user id}/userdetails?fields=string&$skip=int&$top=int&query=string
Parameter Description
fields Optional query parameter. Specifies a subset of the fields to be returned. Use Fields Syntax to define the subset.
$skip Optional query parameter. Number of user details to skip before returning the first entry in the page.
$top Optional query parameter. Maximum number of user details to return in the page.
query

Filter query. See Query Syntax for the definition of supported logical operations syntax. Following fields and tuples are supported for user details:

authLogin: userGithubLogin — All details with the given login

authName: value — All details with the given login

googleID: value — All details with the given OpenID identifier

authName: userGoogleName — All details with the given user full name

has: avatar — Has avatar

authLogin: value — Details with the given login

authLogin: value — All details with the given login

authName: value — All details with the given user full name

authLogin: userLdapLogin — All details with the given login

authName: value — All details with the given login

openID: value — All details with the given OpenID identifier

authName: userOpenIDName — All details with the given user full name

has: avatar — Has avatar

id: value — A user detail with the given id

authMethod: authModule — User details associated with the given auth provider

user: user — User details of the given user

type: authModuleType — User details of the auth providers of the given type

email: email — Details with the given email

has: email — Details with email

jabber: jabber — Details with the given jabber account

has: jabber — Details with jabber

originService: service — Details that were imported from the given service

has: originService — Details that were imported from some service

authLogin: value — Details with the given login

has: authLogin — Details with login

Response

Response Code Meaning
200 OK Successful request.
400 Bad Request Some of the parameters of the request are invalid (for example, required fields in the passed JSON object are missing). The response contains message describing the error.
403 Forbidden Requester has no access to the request.
404 Not Found Requested resource wasn't found.
500 Internal Server Error Failed to process request because of the server error. The response contains message describing the error.

Response body

page

{ "skip": int, /* Requested number of user details to skip before returning the first entry in the page */ "top": int, /* Requested maximum number of user details to return in the page */ "total": int, /* Total number of user details. Returned only if the total field is included as a value of the fields parameter in the query */ "userdetails": [details, ...] }
Last modified: 19 September 2016