Bulk Create Knowledge Items

POST /knowledge-bases/{kb_id}/items

A small batch, written now, answered with the rows.

The nested path is the exception annex 05 §1.2 allows and the reason is the same one it gives: the base is not a filter here, it is the thing being written into. Reading items stays flat at /knowledge-items?kb_id=…, because three of the four placements have no kb_id to nest under.

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 — KnowledgeItemBulkRequest

Field	Type		Notes
items	KnowledgeItemBulkEntry[]	required	—

Responses

Status	Description	Body
201	Successful Response	Page_KnowledgeItemView_
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 \
  -H "Authorization: Bearer $COBRE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
       "items": [
         {}
       ]
     }'

Response — Page_KnowledgeItemView_

Field	Type		Notes
items	KnowledgeItemView[]	required	—
next_cursor	string | null	optional	—
total	integer | null	optional	—