GET /users/{user_id}

Fetch details for a single user in the organization.

You can also fetch details on all users in the organization or by a user's Zulip API email.

Changes: In Zulip 12.0 (feature level 437), fixed a bug dating to feature level 232, which caused guest users to receive fake backwards-compatibility users in the format intended for clients using POST /register without the user_list_incomplete client capability.

New in Zulip 3.0 (feature level 1).

Servers

Path parameters

Name Type Required Description
user_id Integer Yes

The target user's ID.

Query parameters

Name Type Required Description
include_custom_profile_fields Boolean No

Whether the client wants custom profile field data to be included in the response.

Changes: New in Zulip 2.1.0. Previous versions do not offer these data via the API.

Default value: false

client_gravatar Boolean No

Whether the client supports computing gravatars URLs. If enabled, avatar_url will be included in the response only if there is a Zulip avatar, and will be null for users who are using gravatar as their avatar. This option significantly reduces the compressed size of user data, since gravatar URLs are long, random strings and thus do not compress well. The client_gravatar field is set to true if clients can compute their own gravatars.

Changes: The default value of this parameter was false prior to Zulip 5.0 (feature level 92).

Default value: true

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.