This article will help you to understand and get started with the Content Server REST API version 1.0, so you can create your own AppWorks App that connects to Content Server.
OpenText with the release of AppWorks introduced a common API standard that allows a developer to access all OpenText products in a consistent, easy to use manner. Targetted at developers wishing to develop their own AppWorks Service.
An introduction to OpenText Exstream Communication Server v1 API's covering the fundamental details of the available APIs for Document On Demand and Communications scenarios and more on 16.2 release and 16.3. New methods are marked from when they are available, and those methods without mark is available since 16.2.
AppWorks services are server-side applications that typically provide support for AppWorks managed mobile applications (AppWorks apps), forming part of a wider mobile solution. They are deployed by the AppWorks Gateway within its host container (Apache Tomcat 8) along with the aforementioned apps. They are built using the AppWorks Service Development Kit (SDK).
In this article, we go through the development process of a proof of concept app that pulls and displays assets from media manager using a custom angularjs service that enables us to consume of media manager api's. NOTE: This Article applies to AppWorks 1.x NOT AppWorks 16.x
Native push notifications were introduced in version 16 of the AppWorks platform. The AppWorks Gateway can send notifications to registered clients, and the Android and iOS AppWorks mobile clients can receive and process them. This functionality leverages Google Cloud Messaging Services (GCM) to deliver notifications across both platforms seamlessly.