Delete a knowledge source
Soft delete — the row is retained and the index is rebuilt without it. Required scope: `knowledge.write`.
/bots/{botId}/knowledge/sources/{sourceId}Authorization
ApiKeyAuth An external API key, sent as Authorization: Bearer mflo_…. Scopes are checked per route; see each operation’s description.
In: header
Path Parameters
uuiduuidResponse Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X DELETE "https://example.com/bots/497f6eca-6276-4993-bfeb-53cbbbba6f08/knowledge/sources/497f6eca-6276-4993-bfeb-53cbbbba6f08"{ "data": { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "deleted": true }}Create a customer case POST
`title` and `categoryKey` are required. Every referenced record (contact, company, topic, assignee, tags, `links`) must belong to your organisation; an unknown one is a 422 naming the field, never a hint that it exists elsewhere. `companyId` needs an organisation that keeps companies (else 404 `TENANT_MODULE_UNAVAILABLE`). The number is allocated atomically; the case's `source` is `API`. Available to organisations with customer cases switched on: an organisation whose business type has no cases gets 404 `TENANT_MODULE_UNAVAILABLE`, one where cases are not switched on yet gets 403 `FEATURE_NOT_AVAILABLE`. Required scope: `cases.write`.
Get a knowledge source with its content GET
Required scope: `knowledge.read`.