Introduction to Creative Cloud Libraries and Asset Browser APIs
summary
Creative Cloud Libraries API (launched at MAX 2020) lets apps get assets, save assets and subscribe to webhooks for updates; roadmap adds JWT service‑to‑service auth, team libraries, higher upload limits and more collaboration. The web native Asset Browser SDK supplies prebuilt UI components for selective element types and multi‑select; Adobe demos a Magento integration that saves a designer’s image into a shared library and inserts it into a product page, and an Asset Saver SDK is in private beta aiming for Q1 release.
AI-written summary · about
chapters (16)
- 0:00Introduction to session
- 0:24What to expect today
- 1:07Background on Libraries API
- 6:07Key features of Libraries API
- 8:37Libraries API roadmap
- 9:42Getting started with API
- 10:23Introducing Asset Browser SDK
- 11:26Benefits of Asset Browser SDK
- 12:34SDK interface overview
- 15:04Demo setup and personas
- 17:55Creative workflow in demo
- 18:37Marketer workflow in demo
- 20:50Demo recap and next steps
- 21:12Introducing Asset Saver SDK
- 22:48Asset Saver SDK demo
- 23:31Accessing SDKs and Q&A
related talks
45mHow to embed our latest Assets picker into other UI products
19mBringing Adobe's Creative Cloud to the web: Starting with Photoshop
38mSeamless Integration of Experience Manager Assets with Applications
44mWeb APIs You Should Be Using in 2026: Unlocking Next-Level Web Experiences
47mForms that Work - Leveraging Client Libraries & Headless Forms
52mKeynote: Headless Today & Tomorrow with Adobe Experience Manager
24mSuperpowers of browser's Web API
39mAdobe Experience Manager as a Headless CMS - Where/When/Why?