Re-moderate
POST/v1/moderations/{id}/remoderateKey scope moderate
Creates a new moderation from the stored input of an existing one and runs it on the template's current published version. Use it after publishing a new version of a template. For a form only the text and image fields are sent again: the values of number, boolean, enum, url and json fields are not carried over.
Needs a key with the moderate scope. Authentication
Path parameters
idstringRequiredId of the moderation to run again:
mod_plus 22 base62 characters. It must be a top-level moderation whose input is stored.
Returns
Status 200 with the new moderation, or 202 when it was queued because the input has images. The new moderation has its own id, consumes checks like any other and keeps the original's content_id, author_id, context_id and dry_run; metadata.remoderated_from holds the id of the original.
- 200 OKA moderation object
Errors
- 402
quota_exceededThe organisation's remaining monthly checks and extra checks together are fewer than the checks the new moderation needs.
- 403
plan_limitThe organisation's plan no longer includes templates and the original did not run on the basic check.
- 404
not_foundThe key's project has no moderation with this id.
- 404
template_not_foundThe template of the original has been archived.
- 409
is_childThe id belongs to one field of a form. Re-moderate the parent moderation.
- 409
input_not_storedThe input was never stored, or the retention period has passed and it was removed.
Every endpoint can also answer the errors any request can meet: a missing key, a rate limit, a malformed body. Errors
Something missing or unclear on this page? Write to support@useinfrared.com.