# whatsapp.rejected

> The whatsapp.rejected Problem Details code: WhatsApp could not process the request.

Source: https://docs.nexafone.so/v1/errors/whatsapp.rejected/

| | |
| --- | --- |
| HTTP status | `422`, `502` |
| Area | WhatsApp (from Meta) |
| Problem `type` | `https://docs.nexafone.so/errors/whatsapp.rejected` |

## What the `detail` says

The `detail` explains the occurrence; it can read, for example:

- WhatsApp could not process the request.
- WhatsApp rejected the request.

## Handling it

The request is well-formed but its values are not accepted; fix them before retrying.
An upstream service (such as WhatsApp) failed; retry later or follow the message.

## Example

```json
{
  "type": "https://docs.nexafone.so/errors/whatsapp.rejected",
  "title": "Unprocessable Entity",
  "status": 422,
  "code": "whatsapp.rejected",
  "detail": "WhatsApp could not process the request.",
  "requestId": "01J9Z8Q4TQ3W6M5V2X7Y8Z9A0B"
}
```

Match on `code`, never on `detail`: the wording may change. See [Problem Details](/v1/errors/).