Get a stack
Fetches one stack’s metadata by ID (pinned cover, live member count, provenance). The response is metadata only and does not include the stack’s assets — to get its frames, use list_assets with stack_id.
Authorizations
Gumnut API key (apikey_...) sent as a Bearer token in the Authorization header. Create and manage keys in the Gumnut app, or with the API key endpoints while signed in to it.
Path Parameters
Stack ID (with asset_stack_ prefix) to fetch. Carried by the stack_id field on any asset that belongs to a stack.
Response
Successful Response
Represents a group of assets displayed as a single tile.
Unique stack identifier with 'asset_stack_' prefix
Number of live assets in this stack. Excludes trashed members, so it can drop below the number of frames originally grouped.
How a stack came to exist.
auto_burst marks a stack the burst detector created from the time +
EXIF-camera signal; user marks a stack a user created or edited (manual
create, set-cover, add/remove, unstack). The distinction is what keeps
re-detection from stomping a user's correction — the detection pass skips
user stacks.
auto_burst, user When this stack was created
When this stack was last updated
ID of the asset the user pinned as the stack's cover, or null if none is pinned. Null for an auto-detected burst unless a user has since pinned a cover — there is no server-selected default, so a client showing a stack with no pinned cover picks its own. A pinned cover that has been trashed keeps its ID here; it is cleared only once the asset is permanently deleted.