Skip to content

InvitesNotAllowedProblem

The problem of a user who may not create invites of their own now (403, /api/v1/problems/invites-not-allowed); reason says why, and detail says it to the user. Another 403 has none.

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 the user may not create invites of their own now, the first that holds of registration_closed: the registration mode is closed, which takes no new accounts; not_permitted: the instance setting invite_creators is not everyone and the user’s roles lack create_invites; not_approved: the registration of the account is not approved; restricted: the account is suspended or limited.

string
Allowed values: registration_closed not_permitted not_approved restricted

Example generated

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

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

Analytics on this site