2017-12-29 06:36:20 +01:00
|
|
|
# Get all streams
|
|
|
|
|
|
|
|
Get all streams that the user has access to.
|
|
|
|
|
|
|
|
`GET {{ api_url }}/v1/streams`
|
|
|
|
|
|
|
|
## 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-29 06:36:20 +01:00
|
|
|
</ul>
|
|
|
|
<div class="blocks">
|
|
|
|
|
|
|
|
<div data-language="curl" markdown="1">
|
|
|
|
|
|
|
|
```
|
|
|
|
curl {{ api_url }}/v1/streams -u BOT_EMAIL_ADDRESS:BOT_API_KEY
|
|
|
|
```
|
|
|
|
|
|
|
|
You may pass in one or more of the parameters mentioned above
|
|
|
|
as URL query parameters, like so:
|
|
|
|
|
|
|
|
```
|
|
|
|
curl {{ api_url }}/v1/streams?include_public=false \
|
|
|
|
-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-streams|example}
|
2017-12-29 06:36:20 +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 22:50:56 +01:00
|
|
|
// Download zuliprc-dev from your dev server
|
2017-12-29 06:36:20 +01:00
|
|
|
const config = {
|
2018-01-13 22:50:56 +01:00
|
|
|
zuliprc: 'zuliprc-dev',
|
2017-12-29 06:36:20 +01:00
|
|
|
};
|
|
|
|
|
2018-01-13 22:50:56 +01:00
|
|
|
zulip(config).then((client) => {
|
|
|
|
// Get all streams that the user has access to
|
|
|
|
client.streams.retrieve().then(console.log);
|
2017-12-29 06:36:20 +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-streams.md}
|
|
|
|
|
2017-12-29 06:36:20 +01:00
|
|
|
## Response
|
|
|
|
|
|
|
|
#### Return values
|
|
|
|
|
|
|
|
* `stream_id`: The unique ID of a stream.
|
|
|
|
* `name`: The name of a stream.
|
|
|
|
* `description`: A short description of a stream.
|
2018-06-08 22:05:07 +02:00
|
|
|
* `invite-only`: Specifies whether a stream is private or not.
|
|
|
|
Only people who have been invited can access a private stream.
|
2017-12-29 06:36:20 +01:00
|
|
|
|
|
|
|
#### Example response
|
|
|
|
|
|
|
|
A typical successful JSON response may look like:
|
|
|
|
|
2018-01-31 05:04:43 +01:00
|
|
|
{generate_code_example|get-all-streams|fixture}
|
2017-12-29 06:36:20 +01:00
|
|
|
|
2018-06-01 18:52:53 +02:00
|
|
|
An example JSON response for when the user is not authorized to use the
|
|
|
|
`include_all_active` parameter (i.e. because they are not an organization
|
|
|
|
administrator):
|
2017-12-29 06:36:20 +01:00
|
|
|
|
2018-02-16 21:58:03 +01:00
|
|
|
{generate_code_example|user-not-authorized-error|fixture}
|