LinkedIn API Migration

Updated

11 days ago

Overview

To deliver a more consistent and enhanced LinkedIn experience, Sprinklr is upgrading its Distributed integration. Currently, both Finserv and Non-Finserv clients rely on Compliance APIs, while Enterprise users benefit from newer Marketing APIs—creating a capability gap. The new Dual API Model bridges this gap by combining both APIs. It ensures compliance for Finserv clients while enabling advanced publishing, improved reporting, and better performance for all users.

Finserv Clients

LinkedIn API Overview

Sprinklr Distributed currently leverages LinkedIn’s Compliance APIs to support day-to-day user activities such as Publishing, Engagement, Profile Management, and Reporting.

Current State

Distributed users authenticate their LinkedIn accounts within Sprinklr using the Compliance APIs. These APIs power all current platform activities.
Enterprise (SP&E) and Advocacy users, however, use LinkedIn’s newer Marketing APIs, which receive ongoing feature enhancements.

This creates a gap in capabilities between Distributed and Enterprise users.

What’s Changing?

To bridge this gap, Sprinklr is introducing a Dual API Model.

This model enables:

Continued support for compliance use cases
Access to enhanced marketing capabilities

After migration, users will benefit from both Compliance and Marketing APIs.

Dual API Model

Benefits of the Dual API Model

Enhanced Publishing

Users will be able to publish:

Documents
LinkedIn Polls
Fan Profile Mentions (with improved and seamless tagging experience)

Improved Reporting

New metrics will include:

Post Reach
Post Impressions
Total Engagements

Better Performance

Marketing APIs are continuously updated by LinkedIn, resulting in:

Fewer channel-related issues
Improved reliability and performance

Phased Dual API Model Implementation

The migration will take place in two phases:

Soft Migration
Hard Migration

New Authentication Process in the Dual API Model

In the Dual API model, users would need to authenticate twice through their LinkedIn credentials.

After a Distributed user authenticates their LinkedIn profile for the first time, a screen like the one shown below will appear.

They must then click the “Verify” button to complete the second and final step of authentication before the account is added to Sprinklr.

Note: If the user exits, cancels, or refreshes during this process, the account will not be added to Sprinklr.

Soft Migration

Starting in May (post 26.4 release), clients will be able to authenticate their LinkedIn profiles using the Dual API model.

During this phase:

Re-authentication is optional for existing LinkedIn profiles. Users can continue using their accounts with Sprinklr as usual.
Mandatory re-authentication is required only for newly added or re-added accounts. These profiles will immediately gain the combined capabilities of both Marketing and Compliance APIs.

Admin Responsibilities

Admins and Program Managers should guide their Distributed teams to adopt this process and ensure all LinkedIn profiles are re-added using the Dual API model.

Important Notes

Mixing existing and newly added profiles may lead to minor differences in the user experience.
- Example: When publishing from an existing account, the option to Publish Documents may not appear. In contrast, a newly added or re-authenticated account will have this option.
Reporting metrics, such as LinkedIn Post Reach, may be inconsistent if some profiles have been migrated and others have not.

Note: Profile Management and governance will remain unaffected throughout the Soft Migration process.

Hard Migration

Following the Soft Migration grace period, all users are expected to re-add their LinkedIn profiles in Sprinklr using the new two-step authentication process.

For clients who completed migration during Soft Migration, nothing changes—all profiles are already using the Dual API model.
For clients with remaining accounts on the old authentication flow, re-authentication is mandatory. Any profiles not updated will be deactivated in Sprinklr, requiring account owners to re-add them using the Dual API model.

FAQs

LinkedIn API Migration for FinServ Clients

Q1. What is changing for LinkedIn in Sprinklr?
Sprinklr Distributed is moving to a Dual API Model, combining LinkedIn’s Compliance APIs with the newer Marketing APIs. Profiles will use a new two-step authentication and gain both compliance and enhanced marketing capabilities.

Q2. Why is this change happening now?
Enterprise (SP&E) and Advocacy users already use Marketing APIs, which receive most new features. Distributed has been using Compliance APIs only. The Dual API model closes this gap while maintaining compliance.

Q3. What benefits do we get after migrating?

New publishing types: Documents, LinkedIn Polls, easier Fan profile mentions
Enhanced reporting: Post Reach, Post Impressions, Total Engagements
Fewer channel issues thanks to continuous improvements in Marketing APIs

Q4. Will governance or profile management change?
No. Profile management and governance controls remain the same; the migration only adds new capabilities.

Q5. What does the new authentication process look like?
It’s a two-step process:

Sign in with LinkedIn
Click “Verify” to complete authentication

Note: If users exit, cancel, or refresh mid-process, the profile will not be added.

Q6. When do we need to take action?

Soft Migration (starting May): Re-authentication is optional for existing profiles, mandatory for new/re-added accounts.
Hard Migration (post-grace period): All remaining profiles must be re-authenticated or they will be deactivated.

Q7. What happens if our estate is mixed?

Features may differ between legacy and Dual API profiles (e.g., Document publishing not available on old profiles)
Reporting metrics like Post Reach may be incomplete or inaccurate until all profiles are migrated

Q8. Which reporting improvements can we expect?

Post Reach
Post Impressions
Total Engagements

These metrics are only complete for migrated profiles.

Q9. What risks exist if migration is delayed?
Profiles remaining on the old flow will be deactivated during Hard Migration, interrupting publishing and reporting until re-authenticated.

Q10. What should admins and program managers do now?

Communicate the change and timeline
Guide advisors through the two-step authentication
Ensure full migration during Soft Migration to avoid feature gaps, reporting inconsistencies, and last-minute deactivations

Q11. What should advisors do if they don’t see “Publish Documents”?
The profile is likely not on Dual API. Re-add it using the two-step authentication to enable the feature.

Q12. What if reach or engagement metrics are inconsistent?
Check which profiles are migrated. Completing migration across all profiles will normalize reporting.

Q13. Will there be a user guide with screenshots?
Yes. A step-by-step, advisor-facing guide will be provided once the feature is finalized, showing the authentication process visually.

Q14. In one line, what’s our best next step?
Begin Soft Migration early—have admins and advisors re-add all LinkedIn profiles via the two-step flow to unlock new capabilities, ensure accurate reporting, and avoid disruption at Hard Migration.

Non-Finserv Clients

LinkedIn API Overview

Sprinklr Distributed currently uses LinkedIn’s Compliance APIs for Publishing, Engagement, and Reporting.

Current State

Distributed users rely on Compliance APIs
Enterprise (SP&E) and Advocacy users use Marketing APIs. These are newer APIs that will receive upcoming LinkedIn enhancements as they are released.
As a result, there is a gap in capabilities between users onboarded on Distributed and those on Enterprise.