# Report a Wrong Decline

`POST /v1/moderations/appeals`

Tell us a declined request should have been allowed.

Every `422` from content screening carries `error.moderation_id`. Send it here when the decline looks wrong, for example when your end user disputes it. We review every report; a wrong decline gets its rule fixed, so the same request and similar ones pass next time.
Free. One report per decline (sending it again returns the same report). Up to 30 reports a minute per account.

Base URL: `https://api.spicyapi.com`

## Authorizations

- `Authorization` (string, header, required): Bearer authentication header of the form `Bearer <token>`, where `<token>` is your SpicyAPI key (`sk-spicy-…`). Create one in the dashboard under API Keys.

## Body (application/json)

- `moderation_id` (string, required): `error.moderation_id` from the `422` response.
- `reason` (string, optional): Optional: what was intended, up to 1000 characters.

## Request

```bash
curl --request POST \
  --url https://api.spicyapi.com/v1/moderations/appeals \
  --header 'Authorization: Bearer $SPICYAPI_KEY' \
  --header 'Content-Type: application/json' \
  --data '{ "moderation_id": "Xq3f9KcTb2LmNp8RsV4w", "reason": "Adult couple, both 30, nothing violent" }'
```

## Response: 201 application/json

Report received

- `id` (string, required): The moderation_id reported.
- `status` (string, required): `open` until reviewed.

```json
{ "object": "moderation.appeal", "id": "Xq3f9KcTb2LmNp8RsV4w", "status": "open" }
```
