Scope knowledge-records:read for reads · knowledge-records:write for changes
Operations
| GET | /v1/knowledge-records | List — see list |
| POST | /v1/knowledge-records | Create — see create |
| GET | /v1/knowledge-records/{id} | Read — see get |
| PATCH | /v1/knowledge-records/{id} | Update — see update |
| DELETE | /v1/knowledge-records/{id} | Delete — see delete |
Minimal create
curl -X POST https://api2.djcsystem.com/v1/knowledge-records \
-H "Authorization: Bearer $DJC_TOKEN" -H "Content-Type: application/json" \
-d '{ "flowId": "…", "catalogId": "…", "input": "…" }'Fields
Fields you may send on create. Updatable marks fields accepted by PATCH. Anything not listed is server-owned or hidden.
| Field | Type | On create | Updatable |
|---|---|---|---|
flowId | string | required | no |
catalogId | string | required | yes |
input | string | required | yes |
link | string | optional | yes |
Filters & sorting
| Filterable | flowIdcatalogId |
| Sortable | date |
| Default order | id order |
Good to know
- Embeddings are generated asynchronously after a write; a new record becomes searchable by the flow within seconds.
- Keep one fact per record. Changing `input` re-embeds automatically.