Please provide a modern API based on industry standards. That is OAuth, REST, JSON and well documented (in the same way that every other modern API is documented). Preferably make it a swagger API so that generating libraries for various languages can be done automatically.
"Build powerful apps that work with Creative Cloud assets
"The most common actions a CC Storage integration will perform is to download assets stored in Creative Cloud, or to add new content to Creative Cloud. Through RESTful endpoints, your app can interact with CC Cloud Documents, Files, Folders, Libraries, Mobile Creations, file metadata, and published links."We'll be launching the CC Storage API in 2019. Sign up to get the launch announcement."
You could sign up for the launch announcement on that Web page. The whole situation smells like Adobe has defunded this effort, or the senior people on the team have quit, or...
End of Support for the Creative SDK Content Management, Workflow, and Authentication Components
We’re reaching out with an important update about the Creative SDK. Adobe is ending support for the Creative SDK Content Management, Workflow, and Authentication components for iOS, Android, and Web.
Existing integrations of the Creative SDK should continue to work, as we’re not shutting down core services behind the Creative SDK at this time. However, the underlying platform and APIs will be evolving over the next 12-24 months, so we are no longer building the Creative SDK. Therefore, in the best interest of our developer community, we’re no longer supporting new integrations of it. Authentication capabilities will continue to be available. Please see the FAQs for more information.
Here are more details on the end of support to help you plan:
• Adobe is ending support for the Creative SDK Content Management, Workflow, and Authentication components for iOS, Android and Web. The specific Creative SDK features within these components include the Asset Browser UI, CC Files API, CC Libraries API, Lightroom Photos API, Typekit (Fonts) UI, PSD file type read/write, AI file type write, Send to Desktop, and Authentication.
• Existing integrations of the Creative SDK Content Management, Workflow, and Authentication components should continue to work, as we’re not deprecating core services behind the Creative SDK.
• At this point, Adobe is no longer providing developer support for partners working on Creative SDK integrations. Over the next few months, Adobe will remove the Creative SDK Support Center.
• Adobe is no longer reviewing Creative SDK Production Mode ID requests submitted through the Adobe IO console.
• For partners using the Typekit UI, we recommend that you migrate to the Adobe Fonts platform as soon as possible.
• Authentication workflows will continue to be available.
The existing services behind the Creative SDK will continue to function, and some alternatives will be available for developers in the future.
Adobe continues to invest in the developer community, and over the past year, we’ve started several initiatives to support developers that want to integrate with Creative Cloud. We introduced the future of Creative Cloud in-app extensibility with the Unified Extensibility Platform (UXP), and launched the first instance of a UXP-powered ecosystem with XD plugins. Last year, we also launched the Adobe Fund for Design, a $10M fund for entrepreneurs pushing the boundaries of the creative tool ecosystem, and we recently announced the Adobe XD Plugin Accelerator.
You can read more about the recent developments of the Creative Cloud developer ecosystem here, see all of our APIs and SDKs on adobe.io and learn more about the Creative SDK news on our FAQs.