# Problem type: validation-failed

**422 Unprocessable Entity.** The request body is not valid. `errors` lists the messages per field.

`type`: `https://code.salaxy.com/problems/validation-failed`

## When

On the [payment channel config](https://code.salaxy.com/integration/company-settings.md#payment-channel-config) endpoints (v04 beta), a `PUT` or a `PATCH` when, for example:

- A required value is missing or invalid, such as `data.agreementId` or `debitAccount.iban`.
- The body has a field, or a `data` key, that the config does not have.
- A `channel` in the body differs from the path.

A `PATCH` is checked on the result: clearing a required value with `null` fails too. Nothing is saved.

```json
{
  "type": "https://code.salaxy.com/problems/validation-failed",
  "status": 422,
  "title": "The payment channel config is not valid.",
  "errors": {
    "debitAccount.iban": [ "The IBAN is not valid." ],
    "data.agreementId": [ "Required." ]
  }
}
```

`errors` is keyed by the field's path in the request body. The messages follow `Accept-Language` (`fi` or `en`, Finnish by default).

## What to do

Fix the fields that `errors` names. Sending the same request again does not help.

See all [problem types](https://code.salaxy.com/problems/index.md).
