Stores the content moderation configuration and keeps the content_moderation feature flag in step with its is_enabled value.
Recognised keys are is_enabled, profanity_filter, flag_after_threshold, first_comment_approval, auto_flag_user_reject_threshold and auto_flag_user_report_threshold. Any other key sent in config is stored as submitted rather than being discarded, so send only the documented fields.
Endpoint
Method:
POSTPath:
/moderation/configEdition: PRO
Controller:
ModerationController@saveConfigRoute source:
fluent-community-pro/app/Http/Routes/api.php:105Controller source:
fluent-community-pro/app/Http/Controllers/ModerationController.phpRequires the FluentCommunity community-admin permission (or a WordPress super admin).
Requires FluentCommunity Pro. Disabling the feature here also removes the moderation queue routes on the next request.
Live sample
The request and response below were recorded against a running FluentCommunity install and then anonymised — member names, emails, avatars and post content are fictional, and long collections are trimmed to a few entries.
POST Save Moderation Config
Stores the content moderation configuration and keeps the content_moderation feature flag in step with its is_enabled value.
Controller: ModerationController@saveConfig
Route source: fluent-community-pro/app/Http/Routes/api.php:105
Authorizations
WordPress Application Passwords — use Basic auth with username:application_password.
Request Body
Responses
Successful response