Saves the FluentEvent integration settings.
Takes a settings object holding the on/off flag and the events slug. Only those two keys are kept; anything else in the object is dropped. The slug is checked against the portal's own routes and the space sub-pages, so events cannot take a path the community already uses.
Endpoint
Method:
POSTPath:
/settings/fluent-event-settingsEdition: Core
Controller:
SettingController@updateFluentEventSettingsRoute source:
fluent-community/app/Http/Routes/api.php:204Controller source:
fluent-community/app/Http/Controllers/SettingController.phpThe flag is compared against the exact string
yes, sotrue,1andonall save as off.Turning the integration on does not take effect in the same request — the integration is wired up on the next page load.
The endpoint does not check whether the FluentEvent plugin is installed, so it will store an enabled integration with no plugin behind it. Installing the plugin is a separate call.
Re-saving the slug a site already uses is allowed; a slug that sanitises down to nothing fails with the same message as one that is taken.
Inferred sample
No recorded sample exists for this endpoint yet, so the payload below is inferred from the controller and model definitions. Field names and types are accurate; values are placeholders.
POST Post Update Fluent Event Settings
Saves the FluentEvent integration settings.
Controller: SettingController@updateFluentEventSettings
Route source: fluent-community/app/Http/Routes/api.php:204
Authorizations
WordPress Application Passwords — use Basic auth with username:application_password.
Request Body
Responses
Successful response