Skip to main content
POST
Get account knowledge

Restrictions

Usage

  • Always targets the caller’s account knowledge; there is no pack_id parameter. Use POST /safari/knowledge/pack/list to find team knowledge and POST /safari/knowledge/file/list to list its files.
  • If the account has no knowledge yet, an empty one is created on this call, so a valid account never gets not-found here.
  • Any member of the account can read it; pack.can_edit tells whether the caller may change it.

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

No request fields — the account-scope knowledge is always targeted.

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

Account-scope knowledge metadata plus its file list.