2020-06-19 07:30:42 +02:00
|
|
|
# Update personal message flags
|
2018-07-03 18:17:23 +02:00
|
|
|
|
2020-04-28 20:00:46 +02:00
|
|
|
{generate_api_description(/messages/flags:post)}
|
2018-07-03 18:17:23 +02:00
|
|
|
|
|
|
|
## Usage examples
|
|
|
|
|
2018-10-18 00:14:30 +02:00
|
|
|
{start_tabs}
|
|
|
|
{tab|python}
|
2018-07-03 18:17:23 +02:00
|
|
|
|
|
|
|
{generate_code_example(python)|/messages/flags:post|example}
|
|
|
|
|
2018-10-18 00:14:30 +02:00
|
|
|
{tab|js}
|
2018-07-03 18:17:23 +02:00
|
|
|
|
|
|
|
More examples and documentation can be found [here](https://github.com/zulip/zulip-js).
|
|
|
|
|
2020-06-22 00:13:00 +02:00
|
|
|
{generate_code_example(javascript)|/messages/flags:post|example}
|
2018-07-03 18:17:23 +02:00
|
|
|
|
2018-10-18 00:14:30 +02:00
|
|
|
{tab|curl}
|
|
|
|
|
2019-10-09 12:30:12 +02:00
|
|
|
{generate_code_example(curl)|/messages/flags:post|example}
|
2018-07-03 18:17:23 +02:00
|
|
|
|
2018-10-18 00:14:30 +02:00
|
|
|
{end_tabs}
|
2018-07-03 18:17:23 +02:00
|
|
|
|
2020-06-18 15:35:25 +02:00
|
|
|
## Parameters
|
2018-07-03 18:17:23 +02:00
|
|
|
|
|
|
|
{generate_api_arguments_table|zulip.yaml|/messages/flags:post}
|
|
|
|
|
2019-06-04 08:37:14 +02:00
|
|
|
## Available Flags
|
|
|
|
<div>
|
|
|
|
<table>
|
|
|
|
<thead>
|
2019-06-19 10:09:53 +02:00
|
|
|
<tr>
|
|
|
|
<th style="width:30%">Flag</th>
|
|
|
|
<th style="width:70%">Purpose</th>
|
|
|
|
</tr>
|
2019-06-04 08:37:14 +02:00
|
|
|
</thead>
|
|
|
|
<tbody>
|
|
|
|
<tr>
|
|
|
|
<td>`read`</td>
|
|
|
|
<td>
|
|
|
|
Whether the user has read the message. Messages
|
|
|
|
start out unread (except for messages the user
|
|
|
|
themself sent using a non-API client) and can
|
|
|
|
later be marked as read.
|
|
|
|
</td>
|
|
|
|
</tr>
|
|
|
|
<tr>
|
|
|
|
<td>`starred`</td>
|
|
|
|
<td>Whether the user has [starred this message](/help/star-a-message).</td>
|
|
|
|
</tr>
|
|
|
|
<tr>
|
|
|
|
<td>`collapsed`</td>
|
|
|
|
<td>Whether the user has [collapsed this message](/help/collapse-a-message).</td>
|
|
|
|
</tr>
|
|
|
|
<tr>
|
|
|
|
<td>`mentioned`</td>
|
|
|
|
<td>
|
|
|
|
Whether the current user [was
|
2019-06-19 10:09:53 +02:00
|
|
|
mentioned](/help/mention-a-user-or-group) by
|
2019-06-04 08:37:14 +02:00
|
|
|
this message, either directly or via a user
|
|
|
|
group. Not editable.
|
|
|
|
</td>
|
|
|
|
</tr>
|
|
|
|
<tr>
|
|
|
|
<td>`wildcard_mentioned`</td>
|
|
|
|
<td>
|
|
|
|
Whether this message contained [wildcard
|
|
|
|
mention](/help/mention-a-user-or-group#mention-everyone-on-a-stream)
|
|
|
|
like @**all**. Not editable.
|
|
|
|
</td>
|
|
|
|
</tr>
|
|
|
|
<tr>
|
2019-06-27 20:55:15 +02:00
|
|
|
<td>`has_alert_word`</td>
|
2019-06-04 08:37:14 +02:00
|
|
|
<td>
|
|
|
|
Whether the message contains any of the current
|
|
|
|
user's [configured alert
|
|
|
|
words](/help/add-an-alert-word). Not editable.
|
|
|
|
</td>
|
|
|
|
</tr>
|
|
|
|
<tr>
|
|
|
|
<td>`historical`</td>
|
|
|
|
<td>
|
|
|
|
True for messages that the user did not receive
|
|
|
|
at the time they were sent but later was added to
|
|
|
|
the user's history (E.g. because they starred or
|
|
|
|
reacted to a message sent to a public stream
|
|
|
|
before they subscribed to that stream). Not
|
|
|
|
editable.
|
|
|
|
</td>
|
|
|
|
</tr>
|
|
|
|
</tbody>
|
|
|
|
</table>
|
|
|
|
</div>
|
|
|
|
|
2018-07-03 18:17:23 +02:00
|
|
|
## Response
|
|
|
|
|
|
|
|
#### Return values
|
|
|
|
|
2020-05-20 11:57:57 +02:00
|
|
|
{generate_return_values_table|zulip.yaml|/messages/flags:post}
|
2018-07-03 18:17:23 +02:00
|
|
|
|
|
|
|
#### Example response
|
|
|
|
|
|
|
|
A typical successful JSON response may look like:
|
|
|
|
|
|
|
|
{generate_code_example|/messages/flags:post|fixture(200)}
|