ApiKnowledge bases
Hands a managed source's implementation over to the user.
The escape hatch for a stock recipe that is not enough. It flips ownership rather than cloning: the automation, agents and ledger already running stay exactly as they are, with their backlog, history and lineage intact, and become the user's to edit. Knowledge keeps inspecting and reporting on the source and stops being allowed to upgrade or delete its resources — so pause and resume move to the automation, while sync and the activity view go on working. The recipe stamp is kept as provenance. Coming back is a separate, explicit, re-validating adoption.
Authorization
Bearer AuthorizationBearer <token>
JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
knowledgeBase*string
The knowledge base id.
Format
uuidsource*string
The knowledge source id.
Format
uuidtenant*string
The tenant identifier
Response Body
curl -X POST "https://api.fruxon.com/v1/tenants/string/knowledgeBases/497f6eca-6276-4993-bfeb-53cbbbba6f08/sources/497f6eca-6276-4993-bfeb-53cbbbba6f08:fork"{
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"knowledgeBaseId": "619a59ff-6d34-4e0c-9a58-4d2cf062eac9",
"displayName": "string",
"kind": "UNSPECIFIED",
"status": "UNSPECIFIED",
"managementMode": "UNSPECIFIED",
"recipeKey": "string",
"recipeVersion": 0,
"config": null,
"approvalPolicy": "UNSPECIFIED",
"approvalSamplePercent": 0,
"publishPolicy": "UNSPECIFIED",
"settingsEditable": true,
"settingsNotEditableReason": "string",
"resources": [
{
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"resourceKind": "UNSPECIFIED",
"resourceId": "string",
"role": "UNSPECIFIED",
"ownership": "UNSPECIFIED"
}
],
"createdAt": 0,
"modifiedAt": 0
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Empty
Empty
{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}