Symptom
Customers with large media libraries may desire to bulk-upload (mass import) or synchronize thousands of images and digital assets into the Content SaaS platform via API or automation.
Issue
Content SaaS does not recommend or support mass image uploads directly via its native API. Attempting to use APIs for high-volume asset ingestion or bypassing recommended methods may lead to limitations, performance bottlenecks, or support challenges. The CMS is designed for content images (typically smaller media libraries) rather than serving as a large-scale asset repository.
Resolution / Recommended Approach
-
Use a Digital Asset Management (DAM) Integration:
The preferred and supported method for managing and importing large volumes of images is to use an external DAM system. Content SaaS provides out-of-the-box integrations for Bynder and Cloudinary. These integrations allow you to connect your DAM with the CMS and efficiently manage or synchronize a large library of assets.- For Bynder integration, see here: https://documentation.bloomreach.com/content/docs/bynder
-
For Cloudinary integration, see here: https://documentation.bloomreach.com/content/docs/cloudinary
-
Custom DAM Integrations:
If you use a different DAM system, it is possible to implement your own integration to connect with Content SaaS.
Note: If you have specific integration needs, or use a different DAM provider, consult with your implementation partner or Bloomreach support for guidance.
-
Not Recommended: Direct API Upload for Mass Import:
While you can programmatically add individual images via available APIs, bulk or mass imports (such as uploading thousands of images in one operation) are not recommended and may not be supported. The CMS is not designed for use cases involving asset ingestion at this scale.
If you require further assistance about large-scale asset uploads or integration options, please contact Bloomreach Support.