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
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.
A short summary of the problem type, localized from Accept-Language.
The HTTP status code.
An explanation of this occurrence, localized from Accept-Language.
The request ID (the X-Request-Id response header), for reporting the problem.
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.
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.
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