Skip to main content
POST
Delete knowledge file

Restrictions

Usage

  • Deleting is idempotent — removing a file that does not exist succeeds.
  • When other pack files still reference the target, the delete fails with ReferenceExist listing the referrers; set force to proceed (the referrers are returned as warnings).
  • Omitting pack_id targets the account-scope pack; editing the account pack requires account owner/admin, editing a team pack requires team membership.
  • Every call is recorded in the account audit log.

Authorizations

app_key
string
query
required

App key issued from the Flashduty console. Required on every public API call. Keep it secret — it grants the same access as the owning account.

Body

application/json

File to remove from a knowledge pack.

rel_path
string
required

Path of the file relative to the pack root.

pack_id
string

Knowledge pack ID; defaults to the caller's account-scope pack.

force
boolean

Delete even when other pack files reference this file; the referrers are then returned as warnings instead of blocking the delete.

Response

Success

Standard response envelope used by every Flashduty public API. On success data contains the endpoint-specific payload and error is absent. On failure error is present and data is absent. request_id is always present and is also mirrored in the Flashcat-Request-Id response header.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

error
object

Error payload inside the response envelope. Present only on non-2xx responses.

data
object

Deletion result; empty unless warnings were raised.