---
title: "422 — request not accepted"
url: https://lumean.app/de/developers/docs/errors/422
locale: de
description: "The only API response that comes OUTSIDE the common envelope: `{\"message\": \"…\", \"errors\": {\"field\": [\"…\"]}}` — it has no `success` field. Code like `if (!res.success)` works on a 422 only by coincidence, because it is comparing against `undefined`."
generated: 2026-10-17
---

# 422 — request not accepted

- HTTP: `422`

- `Retry-After`-Header: nein

## Was passiert ist

The only API response that comes OUTSIDE the common envelope: `{"message": "…", "errors": {"field": ["…"]}}` — it has no `success` field. Code like `if (!res.success)` works on a 422 only by coincidence, because it is comparing against `undefined`.

## Warum

Two different sources under one code. Request validation — then the body contains `errors` listing the fields. A domain refusal — then there is no `errors`, but there is a `reason`: `content_blocked`, `text_empty`, `text_not_voiceable`, `service_not_found`, `not_allowed`, plus, for bulk chunk retry, `invalid_order_status`, `generative_not_supported`, and `nothing_to_retry`.

## Was zu tun ist

First check whether `errors` is present. If it is, fix the request according to the listed fields. If it is not, but there is a `reason`, the request shape is not the problem, and repeating the same body gets the same refusal; read the page for that specific code.

## Nächste Anfrage

`GET /templates/config-options?service=<code>` — which `config` keys the service accepts at all. The structure depends on the service; do not guess it from examples for other services.

## Verwandt

- [content_blocked — text is on the blocklist](https://lumean.app/de/developers/docs/errors/content-blocked)
- [text_empty — nothing to voice](https://lumean.app/de/developers/docs/errors/text-empty)
- [service_not_found — no such service](https://lumean.app/de/developers/docs/errors/service-not-found)
- [invalid_order_status — order is in the wrong status](https://lumean.app/de/developers/docs/errors/invalid-order-status)
- [Guide: conventions and the response envelope](https://lumean.app/de/developers/docs/guide/conventions)
- [GET /templates/config-options](https://lumean.app/de/developers/docs/api/get-templates-config-options)

---

- Diese Seite im Browser: https://lumean.app/de/developers/docs/errors/422
- Vollständige maschinenlesbare Referenz: https://api.lumean.app/docs/llm.md