Check requirements ambiguity

Flags requirement items that read as vague or ambiguous, by comparing them against known ambiguous-phrasing patterns.

POST /++checkRequirementsAmbiguity

Requirements Analyser

Authentication

Requires an authenticated (logged-in) account.

Request

Content type: application/json

Name	In	Type	Required	Description
`BODY`	body	string	No	—
`items`	body	string	No	—
`threshold`	body	string	No	—
`a`	body	string	No	Sent by the web client (found via frontend call-site tracing).
`ambiguity`	body	string	No	Sent by the web client (found via frontend call-site tracing).
`b`	body	string	No	Sent by the web client (found via frontend call-site tracing).
`conflicts`	body	string	No	Sent by the web client (found via frontend call-site tracing).
`duplicates`	body	string	No	Sent by the web client (found via frontend call-site tracing).

Example request body

{
  "BODY": "example_value",
  "items": [
    "... see the parameters/response fields below for the shape of each entry ..."
  ],
  "threshold": "example_value",
  "a": "example_value",
  "ambiguity": "example_value",
  "b": "example_value",
  "conflicts": "example_value",
  "duplicates": "example_value"
}

Responses

Status	Meaning
`200`	Successful response.
`401`	Unauthorized - authentication required.
`403`	Forbidden - the current user or Integrator registration does not have sufficient permissions.

Example response (illustrative - field names only, values are placeholders)

{
  "issues": "example_value"
}

Requirements Analyser