FruxonDocs
ApiKnowledge bases

Removes a source, and the implementation behind it when Knowledge built that.

What this deletes depends on who owns the implementation. A linked source's resources are the user's, so only the source row and its ownership links go and nothing they point at is touched. A managed source's automation, agents and ledger were created on the user's behalf and are torn down with it — only what is recorded as managed, so a customer's connector configuration survives. Documents already produced are left alone and keep their evidence; deleting generated knowledge is a separate, counted, destructive action. This is also what clears a knowledge base hard-delete that was refused because sources still referenced it. A managed implementation that cannot be fully torn down answers 409 and keeps the source visible so its surviving resources stay findable, and the repair sweep retries it.

DELETE
/v1/tenants/{tenant}/knowledgeBases/{knowledgeBase}/sources/{source}

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.

Formatuuid
source*string

The knowledge source id.

Formatuuid
tenant*string

The tenant identifier

Response Body

curl -X DELETE "https://api.fruxon.com/v1/tenants/string/knowledgeBases/497f6eca-6276-4993-bfeb-53cbbbba6f08/sources/497f6eca-6276-4993-bfeb-53cbbbba6f08"
Empty
{
  "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
}
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}