Rest API
Update the AI configuration
POST /api/v1/ai/configuration
Update how the AI behaves for a workspace: its main language, product name, custom rules, response length, PII filtering and feedback replies.
Notes
- A partial configuration is accepted. Fields you leave out keep their stored value, and derived attributes are recomputed from the merged result
accountIdandwebsiteIdcome from the auth headers; anything the body says about them is ignored- Toggling
optimizerEnabledclears the training-data content hashes, which makes the next ingest re-process every source - A
translationCorpuswhose rows have no recognised language column is rejected with400. That normally means the CSV headers are not language names
Parameters
Section titled “ Parameters ”Header Parameters
Section titled “Header Parameters ”Your API key from account settings.
The email address of your user.
The ID of your account. You can find this in the account settings.
The ID of the workspace you want to use.
Request Body required
Section titled “Request Body required ”object
Primary language the AI answers in, as an ISO code.
Name the AI uses for the product it supports.
Extra instructions applied to every answer.
How long answers should be, e.g. Max.
Words never treated as PII, however the detector scores them.
The languages the AI may answer in when allowAllLanguages is false.
Changing this clears the training-data hashes and forces a full re-ingest.
How many documents are retrieved per question.
Glossary of terms that must translate a fixed way. Rows are keyed by language name.
object
Example
{ "productName": "Unless", "customRules": "Always answer in a friendly tone.", "responseLength": "Max", "suggestReplies": true}Responses
Section titled “ Responses ”The stored configuration.
Bad request - missing body or websiteId, or an invalid translation corpus.
Unauthorized - invalid API key.