Stores the community-wide topic limits — how many topics a post and a space may carry, and whether topics appear on post cards.

Only keys that already exist in the stored config are accepted. The cached config is cleared so the new limits apply to the next post save.

Endpoint

• Method: POST

• Path: /admin/topics/config

• Edition: PRO

• Controller: ProAdminController@updateTopicConfig

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

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

• Requires a community admin, a course admin, or the admin role in the space named by space_id.

• Requires FluentCommunity Pro.

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 Topic Config

POST

/admin/topics/config

Stores the community-wide topic limits — how many topics a post and a space may carry, and whether topics appear on post cards.

Controller: ProAdminController@updateTopicConfig
Route source: fluent-community-pro/app/Http/Routes/api.php:44

Authorizations

ApplicationPasswords

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

Type

API Key (header: Authorization)

Request Body

application/json

{

  

"config": {

  

  

"max_topics_per_post": 0,

  

  

"max_topics_per_space": 0,

  

  

"show_on_post_card": "string"

  

}

}

Responses

Successful response

Content-Type

application/json

{

  

"config": {

  

  

"max_topics_per_post": 0,

  

  

"max_topics_per_space": 0,

  

  

"show_on_post_card": "string"

  

},

  

"message": "string"

}

POST

/admin/topics/config

Playground

Authorization

ApplicationPasswords

Body

Samples

Powered by VitePress OpenAPI