Skip to main content

setSettings

AppWrapper setSettings(id, SetAppSettingsRequest)

PUT /api/2.0/apps/{id}/settings

Save app settings

Stores the application-specific settings document of one portal application for the current portal. The identifier must be an application declared in the installation configuration, as listed by GET api/2.0/apps. The caller must be a portal administrator allowed to edit the portal settings. The call is mutating and idempotent, and it replaces the whole document instead of merging into it: read the current one with GET api/2.0/apps/{id}/settings, change it and send it back complete, or send null to drop the saved document and let the application fall back to its own defaults. Any valid JSON value is accepted, since the content is stored as it is and is interpreted by the application rather than by the portal, while a body that is not valid JSON fails with 400 and stores nothing. The response is the application in its new state, with the stored document echoed back. Unlike PUT api/2.0/apps/{id}/enabled, this operation sends no notification to the connected clients, which pick the new settings up on their next read.

Parameters​

NameInTypeDescriptionNotes
idpathStringThe application whose configuration is stored, by the identifier GET api/2.0/apps reports. An identifier not declared in the installation configuration answers 404.[required] [example: ai-room]
SetAppSettingsRequestbodySetAppSettingsRequestThe configuration to store for this portal, replacing whatever was stored before.[required]

Responses​

Status codeDescriptionTypeResponse headers
200The application in its new state, with the stored settings documentAppWrapperX-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset
400The request body is not a valid JSON document, so no settings are stored--
403The caller has no portal-settings right--
404No application with this identifier is configured on this installation--
401UnauthorizedErrorApiResponse-
429Too Many Requests.ErrorApiResponseRetry-After
500Internal Server Error.ErrorApiResponse-
502Bad Gateway. Returned by the reverse proxy, response body may be HTML and not JSON.--
503Service Unavailable. Returned by the reverse proxy, response body may be HTML and not JSON.--

Return type​

AppWrapper

Authorization​

Basic, OAuth2 (scopes: read, write), ApiKeyBearer, asc_auth_key, Bearer, OpenId

HTTP request headers​

  • Content-Type: application/json
  • Accept: application/json