Skip to main content
POST
Update knowledge pack

Restrictions

Usage

  • scope is the only mutable field; omitting it is a no-op that returns the current pack.
  • For team scope, scope_id is required; for account scope it is set to the account ID automatically.
  • The move fails with ReferenceExist when the destination scope already has a pack — packs are never merged.
  • 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

Move a knowledge pack to a different scope.

pack_id
string
required

Knowledge pack ID to update.

scope
enum<string> | null

Destination scope; omit for a no-op that returns the current pack.

Available options:
account,
team,
null
scope_id
integer<int64> | null

Destination team ID; required when scope is team, set automatically for account.

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

A knowledge pack — a versioned file tree staged into every AI SRE sandbox at session start. One pack exists per (account, scope, scope_id).