2020-06-19 07:30:42 +02:00
|
|
|
# Subscribe to a stream
|
2018-01-06 23:49:14 +01:00
|
|
|
|
2020-04-28 20:00:46 +02:00
|
|
|
{generate_api_description(/users/me/subscriptions:post)}
|
2018-06-26 21:33:13 +02:00
|
|
|
|
2018-01-06 23:49:14 +01:00
|
|
|
## Usage examples
|
|
|
|
|
2018-09-17 16:27:32 +02:00
|
|
|
{start_tabs}
|
|
|
|
{tab|python}
|
2018-01-06 23:49:14 +01:00
|
|
|
|
2019-08-04 13:38:21 +02:00
|
|
|
{generate_code_example(python)|/users/me/subscriptions:post|example}
|
2018-01-06 23:49:14 +01:00
|
|
|
|
2018-09-17 16:27:32 +02:00
|
|
|
{tab|js}
|
2018-01-06 23:49:14 +01:00
|
|
|
|
2018-01-13 23:12:05 +01:00
|
|
|
More examples and documentation can be found [here](https://github.com/zulip/zulip-js).
|
2018-09-17 16:27:32 +02:00
|
|
|
|
2020-06-21 23:37:53 +02:00
|
|
|
{generate_code_example(javascript)|/users/me/subscriptions:post|example}
|
2018-01-13 23:12:05 +01:00
|
|
|
|
2018-09-17 16:27:32 +02:00
|
|
|
{tab|curl}
|
|
|
|
|
2019-10-10 10:19:51 +02:00
|
|
|
{generate_code_example(curl, include=["subscriptions"])|/users/me/subscriptions:post|example}
|
2018-09-17 16:27:32 +02:00
|
|
|
|
|
|
|
To subscribe another user to a stream, you may pass in
|
2020-06-18 15:35:25 +02:00
|
|
|
the `principals` parameter, like so:
|
2018-09-17 16:27:32 +02:00
|
|
|
|
2019-10-10 10:19:51 +02:00
|
|
|
{generate_code_example(curl, include=["subscriptions", "principals"])|/users/me/subscriptions:post|example}
|
2018-01-06 23:49:14 +01:00
|
|
|
|
2018-09-17 16:27:32 +02:00
|
|
|
{end_tabs}
|
2018-01-06 23:49:14 +01:00
|
|
|
|
2020-06-18 15:35:25 +02:00
|
|
|
## Parameters
|
2018-01-20 22:03:05 +01:00
|
|
|
|
2018-06-07 19:47:49 +02:00
|
|
|
{generate_api_arguments_table|zulip.yaml|/users/me/subscriptions:post}
|
2018-01-20 22:03:05 +01:00
|
|
|
|
2018-01-06 23:49:14 +01:00
|
|
|
## Response
|
|
|
|
|
|
|
|
#### Return values
|
|
|
|
|
2020-05-20 11:57:57 +02:00
|
|
|
{generate_return_values_table|zulip.yaml|/users/me/subscriptions:post}
|
2018-01-06 23:49:14 +01:00
|
|
|
|
|
|
|
#### Example response
|
|
|
|
|
|
|
|
A typical successful JSON response may look like:
|
|
|
|
|
2020-04-17 19:16:43 +02:00
|
|
|
{generate_code_example|/users/me/subscriptions:post|fixture(200_0)}
|
2018-01-06 23:49:14 +01:00
|
|
|
|
|
|
|
A typical successful JSON response when the user is already subscribed to
|
|
|
|
the streams specified:
|
|
|
|
|
2020-04-17 19:16:43 +02:00
|
|
|
{generate_code_example|/users/me/subscriptions:post|fixture(200_1)}
|
2018-01-06 23:49:14 +01:00
|
|
|
|
|
|
|
A typical response for when the requesting user does not have access to
|
|
|
|
a private stream and `authorization_errors_fatal` is `True`:
|
|
|
|
|
2020-04-17 19:16:43 +02:00
|
|
|
{generate_code_example|/users/me/subscriptions:post|fixture(400_0)}
|
2018-06-07 19:47:49 +02:00
|
|
|
|
2018-01-06 23:49:14 +01:00
|
|
|
|
|
|
|
A typical response for when the requesting user does not have access to
|
|
|
|
a private stream and `authorization_errors_fatal` is `False`:
|
|
|
|
|
2020-04-17 19:16:43 +02:00
|
|
|
{generate_code_example|/users/me/subscriptions:post|fixture(400_1)}
|