Skip to content

Stores the privacy configuration.

These values feed the visibility checks on the members directory, profile pages, profile space lists, and the username, email and password change controls, so a change here alters what several member-facing endpoints return.

Endpoint

  • Method: POST

  • Path: /settings/privacy-settings

  • Edition: Core

  • Controller: SettingController@updatePrivacySettings

  • Route source: fluent-community/app/Http/Routes/api.php:162

  • Controller source: fluent-community/app/Http/Controllers/SettingController.php

  • Requires the FluentCommunity community-admin permission (or a WordPress super admin).

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 Privacy Settings

POST
/settings/privacy-settings

Stores the privacy configuration.

Controller: SettingController@updatePrivacySettings
Route source: fluent-community/app/Http/Routes/api.php:162

Authorizations

ApplicationPasswords

WordPress Application Passwords — use Basic auth with username:application_password.

Type
API Key (header: Authorization)

Request Body

application/json
JSON
{
  
"settings": {
  
}
}

Responses

Successful response

application/json
JSON
{
  
"message": "string"
}

Playground

Authorization
Body

Samples

Powered by VitePress OpenAPI

FluentCommunity developer documentation