List stacks in a library
Returns a paginated list of stacks — assets grouped for collapsed display, whether detected automatically or grouped by the user — ordered by id: stable, but arbitrary rather than chronological.
list_stacks returns stack metadata only; it does not return the assets inside a stack. To get a stack’s frames, use list_assets with stack_id.
Pagination is cursor-based: when has_more is true, pass the id of the last stack in data as starting_after_id to fetch the next page.
Query Parameters
Library to list stacks from. Optional if the user has a single library; required when they have multiple. Use list_libraries to enumerate.
Return only stacks with this provenance. 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 Return only the stack that pins this asset (with asset_ prefix) as its cover.
Look up specific stacks by ID (max 200; each ID has the asset_stack_ prefix). Accepts multiple ids= query params or a single comma-delimited value (e.g., ids=asset_stack_1,asset_stack_2).
Maximum number of stacks to return per page (1–200). Defaults to 20.
1 <= x <= 200Cursor for pagination. Pass the id of the last stack in the previous response's data to fetch the next page. Omit for the first page.