Moderation

Report a Wrong Decline

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.

POST/v1/moderations/appealsTry it
Report a Wrong Decline
cURL
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" }'
201
JSON
{ "object": "moderation.appeal", "id": "Xq3f9KcTb2LmNp8RsV4w", "status": "open" }

Authorizations

Authorizationstringheaderrequired

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_idstringrequired

error.moderation_id from the 422 response.

reasonstring

Optional: what was intended, up to 1000 characters.

Response

201 · application/json

Report received

idstringrequired

The moderation_id reported.

statusstringrequired

open until reviewed.

Was this page helpful?