Get a user's access history
GET/users/:userId/history
Returns the user's access (JITA) request history and password-management events, newest
first by processed. The list is not paged.
Required role: admin or superadmin for any user; a plain user can read only their
own history (403 for any other user id).
Unknown or malformed userId returns the plain-text 404 Invalid User ID.
Request
Responses
- 200
- 401
- 403
- 404
History entries, newest first.
No token, or the token is invalid or expired. The body is {message}: No auth token provided when no token is sent, otherwise the token check's message (jwt expired, jwt malformed, invalid signature, invalid token, jwt signature is required). Send Authorization: Bearer <token> exactly: the server drops the first seven characters of the header and reads the rest as the token, so a different scheme or an extra space fails. If Authorization is absent, the server reads a token field in the body, then a token query parameter, then x-access-token. Routes that validate query fields reject ?token= with 400 InvalidQuery.
The token's role is not allowed for this operation, or the token's scopes exclude the route
(Scope not allowed by token).
No record has the :id in the path (the id is malformed or unknown). The body is the bare text Invalid <Type> ID (for example Invalid Computer ID, Invalid User ID) with Content-Type text/html; charset=utf-8, not JSON. Some routes return an empty body.