emoji_changed.json

{
  "name": "emoji_changed",
  "desc": "A custom emoji has been added or changed.",
  "long_desc": "The emoji_changed event is sent to all connections for a workspace when that a custom emoji is updated. When they receive this event, clients may either process the subtype if present and of a known value or should update their local cache of emoji by calling the emoji.list method again. An emoji_changed event will always have an event_ts field specified in addition to type. subtype is optional and the presence of additional fields depends on subtype. An emoji_changed event may have a subtype specified. An absent subtype or unrecognized subtype should be handled by reloading all emojis via the emoji.list method. The following is the current list of defined subtypes: An emoji has been added to the emoji list. Note that, like in emoji.list, value is either the URI to fetch the image from or an alias to an existing name as indicated by the alias: pseudo-protocol. One or more emojis have been removed from the emoji list. Note that names is always an array of at least one name, and that aliased emoji entries are always removed when the emoji name they alias to is removed. An emoji has been renamed. It will contain the old_name and new_name. When an event occurs, we will send an HTTP POST request to your Request URL. The outer payload is uniform across all Events API methods, and contains fields like team_id and event. Learn more",
  "required_scope": "RTM",
  "example": {
    "type": "emoji_changed",
    "subtype": "remove",
    "names": [
      "picard_facepalm"
    ],
    "event_ts": "1361482916.000004"
  }
}