Reputation: 55
The call executed is …/users/ with parameter orgDefinedId = “e5555555”.
As per documentation, an array of UserData should be returned.
In practice, when such user doesn’t exist, the call returns 404 "Resource Not Found" (not documented).
Upvotes: 0
Views: 97
Reputation: 3418
This is a documentation oversight. The answer is:
If you used the action with no query parameter filters, the action returns a paged result set containing the users it can find. If, because of the calling user's role permissions, the action can find no users, it returns with a 200 status code, but an empty result set.
If you used the action with a query parameter filter (userName
or orgDefinedId
), the action returns the matching user record(s) it can find; if it can find no matching user(s), the action returns with a 404 status code.
The documentation has been updated to clarify this.
Upvotes: 0