Bulk Curate Knowledge Items

POST /knowledge-bases/{kb_id}/items/curate

curate for a page of one base: one verdict per id, never all-or-nothing (D-5533).

The same floor as the one-item route, because it is the same act repeated. 200 with a verdict per id rather than a 409 for the batch: one item the transition table refuses should not hold back the rest of the review queue. The base itself is a 404 when the caller cannot see it, before any item is read.

Role floor

Requires member 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
kb_id	path	string (uuid)	required	—

Request body — KnowledgeItemBulkCurate

Field	Type		Notes
item_ids	string (uuid)[]	required	—
state	pending | reviewed | promoted | superseded | retired	required	—
reason	string | null	optional	max length 2000

Responses

Status	Description	Body
200	Successful Response	KnowledgeItemBulkCurateResult
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/knowledge-bases/{kb_id}/items/curate \
  -H "Authorization: Bearer $COBRE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
       "item_ids": [
         "0190a2f4-0000-7000-8000-000000000000"
       ],
       "state": "pending"
     }'

Response — KnowledgeItemBulkCurateResult

Field	Type		Notes
results	KnowledgeItemCurateOutcome[]	required	—
curated	integer	required	—
rejected	integer	required	—