I’m sure we wouldn’t design it this way if we built the same endpoint today. But, for historical reasons, some of the Jira Cloud endpoints allow anonymous access. Which means the HTTP request is valid because anonymous may make user search requests. And so is the HTTP response; hence, 200 status. But the empty payload shows the anonymous user does not have permission to see the “kc” user.