---
title: "Set Configuration settings"
method: POST
path: "/configuration"
tags: ["Standard"]
---

# Set Configuration settings

`POST /configuration`

Sets the configuration values for the account. 

It should also validate the settings before saving them, similarly to the `/configuration/validation` endpoint. See `400`(bad request) response for invalid configuration settings.

## Headers

- `TR_ID` string
- `x-lc-signature` string

## Request body

- ConfigurationValue[]
  - `id` string, required — The configuration property ID as defined in the descriptor.
  - `value` union
    - string
    - number
    - integer
    - boolean

## Response `200`

Will return the complete set of latest configurations (even if just one configuration has been updated). Exceptions are the secrets, that should be returned as a string of "*".

- ConfigurationSettingsResult
  - `items` ConfigurationValue[]
    - `id` string, required — The configuration property ID as defined in the descriptor.
    - `value` union
      - string
      - number
      - integer
      - boolean
  - `itemCount` integer — The total number of config values available.

## Other responses

- `400` — Unexpected message structure or data. Error codes: * invalidConfiguration - signals that the configuration has been validated and at least part of it is invalid. The `details` array will contain an element for each field that failed validation. If a pair of fields is invalid (like accountid/accountkey), each field should be added as a separate item in the array. For `code`, you can have the following values: - invalidValue - for values that do not respect certain formats and are validated directly in code. - invalidKey - for secrets that are validated against another API. The actual `value` will not be included in the error response. - nullValue - the field doesn't have a value set and is not optional. * invalidSetup - the setup of the app is not valid. This is used for when the setup is not a valid one, and can include even hard-coded configurations, environment setup, etc. Used mainly for private apps. The UI will show only the `message` to the user.
- `401` — Signature validation failed.

## Changes

- **2026-01-27** (v1) `9d9d8922a0ce` — 2 info
  - the endpoint scheme security `LanguageCloudJWSToken` was removed from the API
  - added the new optional `header` request parameter `x-lc-signature`

[Change history](https://skmtc.dev/rws/apis/app-api/changes/configuration/post.md)

---

[API](https://skmtc.dev/rws/apis/app-api.md) · [All operations](https://skmtc.dev/rws/apis/app-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/rws/app-api/revisions/a06e1ee1c99b/schema)