Get all streams
GET https://webchat.eve-ng.net/api/v1/streams
Get all streams that the user has access to.
Usage examples
#!/usr/bin/env python3
import zulip
# Pass the path to your zuliprc file here.
client = zulip.Client(config_file="~/zuliprc")
# Get all streams that the user has access to
result = client.get_streams()
# You may pass in one or more of the query parameters mentioned above
# as keyword arguments, like so:
result = client.get_streams(include_public=False)
print(result)
More examples and documentation can be found here.
const zulipInit = require("zulip-js");
// Pass the path to your zuliprc file here.
const config = { zuliprc: "zuliprc" };
(async () => {
const client = await zulipInit(config);
// Get all streams that the user has access to
console.log(await client.streams.retrieve());
})();
curl -sSX GET -G https://webchat.eve-ng.net/api/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 -sSX GET -G https://webchat.eve-ng.net/api/v1/streams \
-u BOT_EMAIL_ADDRESS:BOT_API_KEY \
--data-urlencode include_public=false
Parameters
include_public boolean optional
Example: false
Include all public streams.
Defaults to true.
include_web_public boolean optional
Example: true
Include all web-public streams.
Defaults to false.
include_subscribed boolean optional
Example: false
Include all streams that the user is subscribed to.
Defaults to true.
include_all_active boolean optional
Example: true
Include all active streams. The user must have administrative privileges
to use this parameter.
Defaults to false.
include_default boolean optional
Example: true
Include all default streams for the user's realm.
Defaults to false.
include_owner_subscribed boolean optional
Example: true
If the user is a bot, include all streams that the bot's owner is
subscribed to.
Defaults to false.
Response
Return values
Example response(s)
Changes: As of Zulip 7.0 (feature level 167), if any
parameters sent in the request are not supported by this
endpoint, a successful JSON response will include an
ignored_parameters_unsupported array.
A typical successful JSON response may look like:
{
"msg": "",
"result": "success",
"streams": [
{
"description": "A Scandinavian country",
"invite_only": false,
"name": "Denmark",
"stream_id": 1
},
{
"description": "Yet another Italian city",
"invite_only": false,
"name": "Rome",
"stream_id": 2
},
{
"description": "Located in the United Kingdom",
"invite_only": false,
"name": "Scotland",
"stream_id": 3
},
{
"description": "A northeastern Italian city",
"invite_only": false,
"name": "Venice",
"stream_id": 4
},
{
"description": "A city in Italy",
"invite_only": false,
"name": "Verona",
"stream_id": 5
},
{
"description": "New stream for testing",
"invite_only": false,
"name": "new stream",
"stream_id": 6
}
]
}
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):
{
"code": "BAD_REQUEST",
"msg": "User not authorized for this query",
"result": "error"
}