Users can only deactivate custom emoji that they added themselves except for
organization administrators, who can deactivate any custom emoji.
Note that deactivated emoji will still be visible in old messages, reactions,
user statuses and stream descriptions.
Changes: Before Zulip 8.0 (feature level 190), this endpoint returned an
HTTP status code of 400 when the emoji did not exist, instead of 404.
Usage examples
Python
curl
#!/usr/bin/env python3importzulip# Pass the path to your zuliprc file here.client=zulip.Client(config_file="~/zuliprc")# Delete a custom emoji.emoji_name="my_custom_emoji"result=client.call_endpoint(f"realm/emoji/{emoji_name}",method="DELETE")print(result)
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"}
An example JSON response for when no emoji exists with the provided name:
{"code":"BAD_REQUEST","msg":"Emoji 'green_tick' does not exist","result":"error"}