Skip to main content
POST
Remove artifact from gallery

Restrictions

Usage

  • This removes the artifact from the gallery; it does not delete the file. The file stays with its source session and can be published again, which restores the same artifact_id.
  • Requires can_edit on the artifact (the creator, any member of its owning team, or anyone who can manage its source session); otherwise the call fails with AccessDenied.
  • If public sharing was on, the public objects are deleted in the same operation and the link stops resolving. All members’ pins on the artifact are removed.
  • If the source session has been deleted, the file itself is permanently removed 30 days after the artifact is removed from the gallery.
  • Every call is recorded in the account audit log.

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

Identify one gallery artifact.

artifact_id
string
required

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

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
null

Not returned on success; the body carries only request_id.