REQUIREMENTS_NOT_MET

Requirements not met

HTTP status 422 Unprocessable Entity, code REQUIREMENTS_NOT_MET.

What it means#

A transition was refused because the object lacks something a requirement asks for before it: a required checkout question this client cannot answer (its fallback is block), or a field required before the state the transition moves to. error.transition names the transition (checkout, publish, or an action name) and error.missingFields lists what is missing, each with a JSON Pointer (pointer), a label, a reason (required or invalid), requiredBefore and source. The request itself is well formed, which is why this is 422 and not 400. Creating something never answers it; only the transition it gates does.

What to do#

Supply what missingFields names and try again. At checkout, a client that declares complete_form (or redirect) in TL-Client-Capabilities is asked for the answers instead of being refused.

On the wire#

Every error response carrying this code names this page in error.moreInfo, with the request id in the query string. See Error codes for the response shape and the list of every code.