mirror of https://github.com/zulip/zulip.git
47 lines
1.1 KiB
Markdown
47 lines
1.1 KiB
Markdown
# Upload custom emoji
|
|
|
|
{generate_api_description(/realm/emoji/{emoji_name}:post)}
|
|
|
|
## Usage examples
|
|
|
|
{start_tabs}
|
|
|
|
{tab|python}
|
|
|
|
{generate_code_example(python)|/realm/emoji/{emoji_name}:post|example}
|
|
|
|
{tab|curl}
|
|
|
|
{generate_code_example(curl)|/realm/emoji/{emoji_name}:post|example}
|
|
|
|
{end_tabs}
|
|
|
|
|
|
## Parameters
|
|
|
|
As described above, the image file to upload must be provided in the
|
|
request's body.
|
|
|
|
## Emoji name
|
|
|
|
The emoji name can only contain letters, numbers, dashes, and spaces.
|
|
Upper and lower case letters are treated the same, and underscores (_)
|
|
are treated the same as spaces (consistent with how the Zulip UI
|
|
handles emoji).
|
|
|
|
## Maximum file size
|
|
|
|
The maximum file size for uploads can be configured by the
|
|
administrator of the Zulip server by setting `MAX_EMOJI_FILE_SIZE`
|
|
in the [server's settings][1]. `MAX_EMOJI_FILE_SIZE` defaults
|
|
to 5MB.
|
|
|
|
[1]: https://zulip.readthedocs.io/en/latest/subsystems/settings.html#server-settings
|
|
|
|
## Response
|
|
#### Example response
|
|
|
|
A typical successful JSON response may look like:
|
|
|
|
{generate_code_example|/realm/emoji/{emoji_name}:post|fixture(200)}
|