Skip to main content
POST
Delete knowledge

Restrictions

Usage

  • Removes the knowledge and every file it contains; there is no API to restore it.
  • Requires can_edit on the knowledge: the account owner or an admin for account knowledge, membership of the team for team knowledge.
  • Deleting the account knowledge is allowed; the next POST /safari/knowledge/get (or file call without pack_id) creates a new empty one.
  • Every call is recorded in the account audit log.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

Body

application/json

Knowledge to delete.

pack_id
string
required

Knowledge ID to 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.