Pain:  Our editors have to navigate a mix of custom-developed and legacy CMS system interfaces and third-party software to work with and manage our content. Integrating these systems has proven to be difficult, costly and time-consuming, particularly when dealing with proprietary or poorly documented APIs

Pill:  Openstore, OpenstoreAPI

Description:  By using the OpenstoreAPI to roll out custom user interfaces and by taking full advantage of Openstore’s API interfaces, all connected legacy systems will be able to have an efficient, consistent and streamlined flow of content between themselves, the CMS and all production environments.  These APIs provide for the possibility of seamless integration with other business applications as well (e.g., e-commerce platforms, marketing systems, or publishing tools), reducing data silos across the company and increasing operational efficiency.

Proof:  Installing Openstore as our primary image search and retrieval interface and connecting it with our legacy CMS was straightforward and has helped increase our newsroom’s efficiency.  Openstore’s ability to non-disruptively connect third-party software with legacy systems is also being used to enable internal test users to explore the potential of AI-enabled tools in selected parts of their daily workflows without having to pre-configure extensive test environments.

Keywords: CMS, OpenstoreAPI, Third party software

• Develop own user interfaces with OpenstoreAPI to full integration in own systems

• Upload content used to Openstore via OpenstoreAPI (ADD_IMAGE / ADD_VIDEO / ADD_ARTICLE / ADD_PDF)

• Search, View info, Fetch, Update content, add info of publications etc via OpenstoreAPI...

• Online documation and TEST bench for all API calls within OpenstoreAPI dokumentation

• Easy to use API, used by many different third party developers

• 160+ API calls, and still adding new ones to fully support all third party developers building more and more applications...