Skip to main content
PUT
Edit quality assurance settings

Authorizations

Authorization
string
header
required

Get a token from auth/login endpoint and then pass it in the Authorization HTTP header in every subsequent API call. For more information visit our help center.

Path Parameters

projectUid
string
required

Project UID

Body

application/json

QA settings

checks
object[]

List of QA check configurations. Each entry must include "name" (check identifier) and "type" (VOID, NUMBER, STRING, REGEX, or MORAVIA). VOID, NUMBER, and STRING checks accept "enabled", "ignorable", "instant", and "lock"; MORAVIA accepts "enabled", "ignorable", "instant", and a "profile" string; REGEX checks carry a "rules" array (per-rule fields define the regular expressions and flags). NUMBER checks require a numeric "value"; STRING checks accept a string "value". Only checks listed here are updated; omitted checks keep their current settings. The "strictJobStatus" check name is a special case: it is not a content/segment-level QA rule but the project/template-wide completion gate — setting its "enabled" to true blocks linguists from setting a job to Completed while QA warnings are unresolved for that job. Its "ignorable" has no effect for this check name.

Example:

"\n {\n \"ignorable\": false,\n \"enabled\": true,\n \"type\": \"VOID\",\n \"instant\": false,\n \"name\": \"emptyTarget\"\n },\n {\n \"ignorable\": false,\n \"enabled\": true,\n \"value\": 12,\n \"type\": \"NUMBER\",\n \"name\": \"targetLength\"\n },\n {\n \"ignorable\": false,\n \"enabled\": true,\n \"value\": \"ASAP, irony\",\n \"type\": \"STRING\",\n \"instant\": true,\n \"name\": \"forbiddenStrings\"\n },\n {\n \"enabled\": true,\n \"profile\": \"jiris\",\n \"ignorable\": true,\n \"type\": \"MORAVIA\",\n \"name\": \"moravia\"\n },\n {\n \"rules\": [\n {\n \"description\": \"Description\",\n \"sourceRegexp\": \".+\",\n \"targetRegexp\": \".+\",\n \"ignorable\": true\n },\n {\n \"description\": \"Description\",\n \"sourceRegexp\": \"i+\",\n \"targetRegexp\": \"e+\",\n \"ignorable\": false\n }\n ],\n \"type\": \"REGEX\",\n \"name\": \"regexp\"\n },\n {\n \"enabled\": true,\n \"ignorable\": true,\n \"type\": \"VOID\",\n \"name\": \"customQa\"\n }\n "

Response

OK

checks
object[]

List of QA check configurations. The "strictJobStatus" check is a special case: it is not a content/segment-level QA rule but the project/template-wide completion gate — setting its "enabled" to true blocks linguists from setting a job to Completed while QA warnings are unresolved for that job. Its "ignorable" has no effect for this check name.