Assets
The library that sits on the processing spine
DAM with search, metadata, rights, and collections — fed by image pipelines and library ingest. Processing history stays attached where we already wire it; Flows can inspect and transform images from the same library.
What you get
Unified library
Images, video, and objects in one searchable surface with collections for campaigns and sets.
Metadata that operators own
Title, alt, description, and tags on images today — queryable with faceted tag search.
Governance & rights
Policies for signed delivery, IP bind, and rights windows — retention on image trash.
Linked processing history
See which transform, watermark, or VOD job produced each derivative when that job recorded lineage.
Differentiation
Assets platform depth
- Search across images, objects, and video jobs
- Collections (cross-type campaign sets)
- Image metadata and tag facets
- Rights windows and signed-URL policies
- Folder ACL for API keys
- Lineage to image variants and encode jobs
- RBAC aligned to org → workspace → project
- Brand kits and nested collections
- Connector sync from customer storage
Example
Same auth and tenancy headers as the rest of the API. Where a capability plugs into Flows today, that is called out on the product page — we do not imply every media type shares one live pipeline yet.
GET /v1/collections + GET /v1/images
# DAM collections
curl "https://api.sialflow.com/v1/collections" \
-H "Authorization: Bearer $SIALFLOW_API_KEY" \
-H "X-SialFlow-Project-ID: $SIALFLOW_PROJECT_ID"
# Image search (library browse)
curl "https://api.sialflow.com/v1/images?q=hero&tag=product" \
-H "Authorization: Bearer $SIALFLOW_API_KEY" \
-H "X-SialFlow-Project-ID: $SIALFLOW_PROJECT_ID"Ship with Assets
Open the portal, follow the docs, or talk to us about rollout for your agency or commerce stack.