Answer Open Question

POST /open-questions/{item_id}/answer

The question is a knowledge_item, so the path parameter is item_id.

It reads as a detail and it is the contract: the operation id names a generated SDK method and the path names its argument, and both are frozen (D-053).

Role floor

Requires admin or above. The floor is a minimum, not a grant: scope filtering still applies on top of it, and a resource in another tenant answers 404 rather than 403.

Parameters

Name	In	Type		Notes
item_id	path	string (uuid)	required	—

Request body — OpenQuestionAnswer

Field	Type		Notes
content	string	required	min length 1 max length 8000
audience	string	optional	Default "kb".
knowledge_set	string (uuid) | null	optional	—

Responses

Status	Description	Body
200	Successful Response	OpenQuestionView
422	Validation Error	HTTPValidationError

Only the success paths are declared

Any operation may also answer any status in the error catalogue, and every failure body is the platform envelope — including the 422 this document types as HTTPValidationError.

Example

The body shows the fields the schema always carries. Which combination is legal is a service rule the schema cannot express, so read the description above before copying this.

curl -X POST https://your-deployment.example.com/open-questions/{item_id}/answer \
  -H "Authorization: Bearer $COBRE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
       "content": "string"
     }'

Response — OpenQuestionView

Field	Type		Notes
id	string (uuid)	required	—
question	string	required	—
asked	integer	required	—
contexts	string[]	optional	—
closable	boolean	optional	Default false.
nearest_similarity	number	optional	Default 0.0.
answered_by	string (uuid) | null	optional	—