Skip to content

CustomEmojiRequestProblem

The problem of a custom emoji request that cannot be decided or withdrawn (409, /api/v1/problems/custom-emoji-request-conflict); reason says why.

object
type
required

A URI that identifies the problem type, stable for clients to branch on. It is about:blank when the problem means no more than its HTTP status.

string format: uri-reference
title
required

A short summary of the problem type, localized from Accept-Language.

string
status
required

The HTTP status code.

integer
>= 400 <= 599
detail

An explanation of this occurrence, localized from Accept-Language.

string
request_id

The request ID (the X-Request-Id response header), for reporting the problem.

string
field

The member of the request that a 422 is about, by its name in the request: a property of the JSON body by its path (display_name, fields[].name, poll.options[1]), a form field, a query parameter, or a header (Idempotency-Key). detail then says what is wrong with its value without naming it, for the client to show beside that field. Absent when the problem is not about one member.

string
reason

Why a custom emoji request cannot be decided or withdrawn. not_pending: it was already approved, rejected, withdrawn, or lapsed. requester_cannot_create: the requester no longer holds create_custom_emojis or can no longer use the server. shortcode_taken: a local emoji has the shortcode of the request. The last two can only be rejected.

string
Allowed values: not_pending requester_cannot_create shortcode_taken

Example generated

{
"type": "example",
"title": "example",
"status": 1,
"detail": "example",
"request_id": "example",
"field": "example",
"reason": "not_pending"
}

For LLMs and coding agents:llms.txt,llms-full.txt, llms-small.txt

Analytics on this site