PATCH /navigation_views/{fragment}
Update the details of an existing configured navigation view, such as its name or whether it's pinned.
Changes: New in Zulip 11.0 (feature level 390).
Servers
- https://{subdomain}.zulipchat.com/api/v1
- {server}/api/v1
- https://chat.zulip.org/api/v1
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
fragment |
String | Yes |
The unique URL hash of the navigation view to be updated. This also serves as the identifier for the navigation view. |
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 |
|---|---|---|---|
is_pinned |
Boolean | No |
Determines whether the view is pinned (true) or hidden in the menu (false). |
name |
String | No |
The user-facing name for custom navigation views. Omit this field for built-in views. |
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.