stacks

Remove assets from a stack

Changed on

Pulls one or more frames out of the stack. The assets themselves are untouched — they remain in the library (and in any albums) and simply appear as individual photos again. IDs that are not current members of the stack are silently ignored.

If a removed frame was the pinned cover, the pin is cleared with no automatic re-pick — clients choose their own display cover. A stack that survives the removal is marked user-owned (origin = user) so burst re-detection honors the edit; a removal that leaves fewer than 2 members dissolves the stack entirely, returning its remaining frames to loose display too. Trashed frames still count as members for that threshold (unlike asset_count, which excludes them), so a stack can survive with asset_count below 2.

delete/api/stacks/{stack_id}/assets

Request

  • Base URL: https://api.gumnut.ai
  • URL: https://api.gumnut.ai/api/stacks/{stack_id}/assets
  • Auth: one of:
    • HTTP bearer
    • HTTP bearer

Path parameters

stack_idstring required

Stack ID (with asset_stack_ prefix) of the stack to pull frames out of.

Request body

asset_idsstring[] required

Asset IDs (with asset_ prefix) to pull out of the stack. Get member IDs from list_assets with stack_id. Up to 200 ids per request.

Response

Successful Response

DeletionResponse required

Empty acknowledgment returned when an operation succeeds.

Changes

  • 815e0302a988Revision changes
    • breaking

      response property detail list-of-types was widened by adding types string to media type application/json of response 422

    • info

      the response property became required for the status

  • c3e15c78f2daRevision changes
    • info

      added the media type application/json for the response with the status

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status