Hello, I have just opened a PR [1] to merge the streams-provider-sprinklr module into apache-streams/master. This module provides wrappers around some of the data structures and endpoints exposed by Sprinklr's API, especially the ones concerned with social media data.
Sprinklr is a software company managing a SaaS platform that serves lots of different roles, but the ones relevant here are as a social media data warehouse and listening platform. This module only wraps a small portion of the exposed Sprinklr API, but is designed to be extensible, and to provide full vertical integration for a specific use case: extracting social data for accounts authenticated within the Sprinklr platform. The general workflow is to use the endpoint implemented in the Bootstrap interface to get a list of the social accounts authenticated in the user's Sprinklr environment. Those accounts can then be passed on to the endpoints implemented in the Profiles interface to retrieve data about the authenticated accounts and about the accounts engaging with authenticated accounts, as well as about the engagements themselves. Sprinklr API documentation can be found at [2]. There are a few logical next steps for development of this module: 1. The endpoints and jsonschema objects I've implemented so far work with v1 of the Sprinklr API. There are also a host of v2 endpoints with their own data structures and workflows. These endpoints are not very mature yet, but do expose some functionality that doesn't exist in the v1 endpoints. 2. There are several endpoints within v1 of the Sprinklr API which I have not yet implemented, including POST endpoints like profile search and profile update. 3. Sprinklr exposes a host of reporting endpoints intended to provide high-level summary statistics of social activity and engagement metrics for building dashboards. None of these have been implemented. Thanks, Brian Hodge [1] https://github.com/apache/streams/pull/493 [2] https://developer.sprinklr.com/docs/read/API_Overview
