Save a new immutable document revision
PATCH
/v1/knowledge/{libraryId}/documents/{documentId}How to call this endpoint
Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.
Path, query, and header parameters
These parameters control which ACP object the endpoint acts on and how the request is processed.
Path parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| libraryId | path | string | Yes | Knowledge library ID |
| documentId | path | string | Yes | Stable Knowledge document ID |
Query parameters
None.
Body schema
Content type: application/json · Required
| Field | Type | Required | Description |
|---|---|---|---|
| title | string | No | Display title. |
| summary | string | No | — |
| markdown | string | No | — |
| content | string | No | Raw text content. |
| slug | string | No | — |
| parentDocumentId | string | No | — |
| sortOrder | integer | No | — |
| provenance | object | No | — |
| baseRevisionId | string | No | Optimistic-concurrency base revision. A stale value returns HTTP 409. |
What the API returns
Each response code below includes the documented payload shape for the ACP API.
200Knowledge document updated
None.
409Base revision is stale
None.
Save a new immutable document revision
Loading...
Response 200
Loading...