POST /messages/{message_id}/typing
Notify other users whether the current user is editing a message.
Typing notifications for editing messages follow the same protocol as set-typing-status, see that endpoint for details.
Changes: Before Zulip 10.0 (feature level 361), the endpoint was
named /message_edit_typing with message_id a required parameter in
the request body. Clients are recommended to start using sending these
typing notifications starting from this feature level.
New in Zulip 10.0 (feature level 351). Previously, typing notifications were not available when editing messages.
Servers
- https://{subdomain}.zulipchat.com/api/v1
- {server}/api/v1
- https://chat.zulip.org/api/v1
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
message_id |
Integer | Yes |
The target message's ID. |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/x-www-form-urlencoded" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
op |
String | Yes |
Whether the user has started ( Valid values:
|
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.