We know how easy it is to use APIs when they're structured to work with your existing code and libraries. SocialOS provides four API formats to provide both flexibility and accessibility:
The Native API provides the most comprehensive functionality, supporting user management and authentication, public and private message streams, contact management, triggers, webhooks, CRM and CMS functionality, and advanced filters, feeds, and analytics.
The Parse-compatible API provides a superset of the functionality of the Parse open-source server, including user management, basic analytics, custom classes, push notifications, cloud functions, and triggers.
The Slack-compatible API provides functionality compatible with the Slack Web, Events, and Conversations APIs. This supports user, team, channel, and content management, webhooks, and bot support.
The Twitter-compatible API provides core support for Twitter-compatible messaging, including public and direct messages, lists, friends, followers, muting and blocking, plus extensions for user management and message channels.
Information created via any supported API is automatically compatible with all other APIs. Messages posted via the Twitter-compatible API can be routed to a Slack bot or pushed to a mobile app using the a Parse API library. Fields and data structures are mapped by the compatibility service to conform with the standards of each supported API.
The Native API provides a superset of the functionality of the Compatibility APIs. When functions are needed beyond those supported by the Compatibility Service, the Native API can be used to provide those additional functions to the application without needing to change any existing code.
Updated about 6 years ago