Skip to main content
POST
Ensure knowledge pack

Restrictions

Usage

  • Idempotent: if a pack already exists at (scope, scope_id), it is returned unchanged.
  • For account scope, scope_id is ignored (the account ID is used) and a default DUTY.md is seeded on first creation.
  • Creating the account-scope pack requires account owner/admin; creating into a team requires membership of that team.
  • 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

Scope at which to ensure a knowledge pack exists.

scope
enum<string>
required

Scope of the pack to ensure. One of: account (account-level pack; scope_id is forced to the caller's account ID and only account admins may create it; first creation seeds a default DUTY.md), team (team-level pack; the scope_id team ID is required and the caller must belong to that team).

Available options:
account,
team
scope_id
integer<int64>

Team ID; required for team scope, ignored for account scope.

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).