Skip to main content
POST
Update artifact

Restrictions

Usage

  • Only the provided fields change — omit title or team_id to leave them unchanged.
  • team_id: 0 moves the artifact to personal scope (only the creator can manage it); a positive team_id requires the caller (for app_key calls, the key owner) to be a member of that team.
  • Returns the full artifact after the update.
  • 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

Partial update of a gallery artifact. Only provided fields change.

artifact_id
string
required

Artifact ID (art_ prefix). Also the key of the public-share link.

title
string | null

New title. Trimmed; must be non-empty when provided. Omit to leave unchanged.

team_id
integer<int64> | null

Transfer target scope. 0 moves the artifact to personal scope (only the creator can manage it); a positive value moves it to a team the caller must belong to. Omit to leave unchanged.

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

One published artifact in the gallery. Time fields are Unix timestamps in milliseconds.