Upload knowledge file
Create or overwrite a file in a knowledge pack with base64-encoded content.
Restrictions
Usage
- The file body is sent as base64 text in the JSON field
content_b64— this is not a multipart upload. - Writing an existing
rel_pathoverwrites it;content_typeis inferred from the extension when omitted (.md→text/markdown). - Content must decode to valid UTF-8 text; binary payloads are rejected with
InvalidParameter. - Editing the account-scope pack requires account owner/admin; editing a team pack requires team membership.
- Every call is recorded in the account audit log.
Authorizations
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
File to create or overwrite. The body is base64 text in content_b64, not a multipart upload.
Destination path relative to the pack root; existing files are overwritten.
Knowledge pack ID; defaults to the caller's account-scope pack.
Base64-encoded file content; must decode to valid UTF-8 text.
MIME type; inferred from the file extension when omitted.
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.
Unique ID for this request. Mirrored in the Flashcat-Request-Id header. Include it when reporting issues.
"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"
Error payload inside the response envelope. Present only on non-2xx responses.
The written file plus any non-blocking warnings.