2017-12-30 04:09:58 +01:00
|
|
|
# Get all users
|
|
|
|
|
|
|
|
Retrieve all users in a realm.
|
|
|
|
|
|
|
|
`GET {{ api_url }}/v1/users`
|
|
|
|
|
|
|
|
## Usage examples
|
|
|
|
<div class="code-section" markdown="1">
|
|
|
|
<ul class="nav">
|
|
|
|
<li data-language="python">Python</li>
|
|
|
|
<li data-language="javascript">JavaScript</li>
|
2018-01-22 22:49:30 +01:00
|
|
|
<li data-language="curl">curl</li>
|
2017-12-30 04:09:58 +01:00
|
|
|
</ul>
|
|
|
|
<div class="blocks">
|
|
|
|
|
|
|
|
<div data-language="curl" markdown="1">
|
|
|
|
|
|
|
|
```
|
|
|
|
curl {{ api_url }}/v1/users -u BOT_EMAIL_ADDRESS:BOT_API_KEY
|
|
|
|
```
|
|
|
|
|
|
|
|
You may pass the `client_gravatar` query parameter as follows:
|
|
|
|
|
|
|
|
```
|
|
|
|
curl {{ api_url }}/v1/users?client_gravatar=true \
|
|
|
|
-u BOT_EMAIL_ADDRESS:BOT_API_KEY
|
|
|
|
```
|
|
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
<div data-language="python" markdown="1">
|
|
|
|
|
2018-02-16 04:09:21 +01:00
|
|
|
{generate_code_example(python)|get-all-users|example}
|
2017-12-30 04:09:58 +01:00
|
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
<div data-language="javascript" markdown="1">
|
|
|
|
More examples and documentation can be found [here](https://github.com/zulip/zulip-js).
|
|
|
|
```js
|
|
|
|
const zulip = require('zulip-js');
|
|
|
|
|
2018-01-13 23:27:10 +01:00
|
|
|
// Download zuliprc-dev from your dev server
|
2017-12-30 04:09:58 +01:00
|
|
|
const config = {
|
2018-01-13 23:27:10 +01:00
|
|
|
zuliprc: 'zuliprc-dev',
|
2017-12-30 04:09:58 +01:00
|
|
|
};
|
|
|
|
|
2018-01-13 23:27:10 +01:00
|
|
|
zulip(config).then((client) => {
|
|
|
|
// Get all users in the realm
|
|
|
|
client.users.retrieve().then(console.log);
|
2017-12-30 04:09:58 +01:00
|
|
|
|
2018-01-13 23:27:10 +01:00
|
|
|
// You may pass the `client_gravatar` query parameter as follows:
|
|
|
|
client.users.retrieve({client_gravatar: true}).then(console.log);
|
2017-12-30 04:09:58 +01:00
|
|
|
});
|
|
|
|
```
|
|
|
|
</div>
|
|
|
|
|
|
|
|
</div>
|
|
|
|
|
|
|
|
</div>
|
|
|
|
|
2018-01-20 22:03:05 +01:00
|
|
|
## Arguments
|
|
|
|
|
|
|
|
**Note**: The following arguments are all URL query parameters.
|
|
|
|
|
|
|
|
{generate_api_arguments_table|arguments.json|get-all-users.md}
|
|
|
|
|
2017-12-30 04:09:58 +01:00
|
|
|
## Response
|
|
|
|
|
|
|
|
#### Return values
|
|
|
|
|
|
|
|
* `members`: A list of dictionaries where each dictionary contains information
|
|
|
|
about a particular user or bot.
|
|
|
|
* `email`: The email address of the user or bot..
|
|
|
|
* `is_bot`: A boolean specifying whether the user is a bot or not.
|
|
|
|
* `avatar_url`: URL to the user's gravatar. `None` if the `client_gravatar`
|
|
|
|
query paramater was set to `True`.
|
|
|
|
* `full_name`: Full name of the user or bot.
|
|
|
|
* `is_admin`: A boolean specifying whether the user is an admin or not.
|
|
|
|
* `bot_type`: `None` if the user isn't a bot. `1` for a `Generic` bot.
|
|
|
|
`2` for an `Incoming webhook` bot. `3` for an `Outgoing webhook` bot.
|
|
|
|
`4` for an `Embedded` bot.
|
|
|
|
* `user_id`: The ID of the user.
|
|
|
|
* `bot_owner`: If the user is a bot (i.e. `is_bot` is `True`), `bot_owner`
|
|
|
|
is the email address of the user who created the bot.
|
|
|
|
* `is_active`: A boolean specifying whether the user is active or not.
|
|
|
|
|
|
|
|
#### Example response
|
|
|
|
|
|
|
|
A typical successful JSON response may look like:
|
|
|
|
|
2018-02-07 04:25:23 +01:00
|
|
|
{generate_code_example|get-all-users|fixture}
|