Your employees’ LinkedIn accounts are not an integration detail.
When you roll employee advocacy out to 20, 50 or 100 people, the connection to LinkedIn becomes part of the product decision. Buyers should understand the authorisation model, the permissions requested and how publishing and measurement actually work.
Ripply has approved access to LinkedIn’s official APIs for its LinkedIn workflows.
LinkedIn’s OAuth 2.0 flow lets members grant application permissions through LinkedIn rather than sharing their LinkedIn password with the application.
API access does not remove the need for employee choice and governance. Ripply’s workflow is designed around Marketing guardrails and employee participation.
LinkedIn does not make all API capabilities open to every app.
LinkedIn describes the Community Management API as a vetted product with Development and Standard tiers. Access is requested through LinkedIn, and Standard Tier is the full-featured production tier that requires an upgrade application and review.
LinkedIn also states that applications must be authorised and authenticated before accessing LinkedIn data or member information. Member access uses OAuth 2.0: the LinkedIn member grants permissions to the application, and the application receives the authorised access needed for the approved workflow.
Five questions to ask every employee advocacy vendor.
Ask the vendor to name the supported integration rather than saying only that it “integrates with LinkedIn.”
Understand whether the workflow relies on an approved LinkedIn API programme and what access tier supports production use.
Ask what employees see, which permissions are requested and whether LinkedIn itself handles the authorisation step.
Make the vendor demonstrate the exact live workflow you plan to use, including any limitations created by LinkedIn’s API.
Serious vendors should be able to explain versioning, permissions and how they maintain supported integrations over time.
We would rather be precise than hide behind a badge.
“Ripply has approved access to LinkedIn’s official APIs.”
That is the trust message. It is specific, verifiable and relevant to a buyer. We do not describe API approval as an endorsement, and we do not use “LinkedIn Partner” as a catch-all label.
For B2B marketing teams, the practical benefit is confidence that the LinkedIn layer of the product is built around LinkedIn’s recognised application and authorisation framework.
Sources
LinkedIn changes its APIs and access programmes over time. These references were reviewed on 6 September 2026.
Questions buyers ask
Does Ripply use the official LinkedIn API?
Yes. Ripply has approved access to LinkedIn’s official APIs and uses LinkedIn’s member authorisation model for relevant LinkedIn workflows.
Does Ripply need an employee’s LinkedIn password?
No. LinkedIn uses OAuth 2.0 member authorisation. The member grants the requested permissions through LinkedIn rather than giving Ripply their LinkedIn password.
Is approved LinkedIn API access the same as being an official LinkedIn Partner?
No. They are different claims. Ripply describes its status precisely as having approved access to LinkedIn’s official APIs.
Why does LinkedIn API access matter?
It helps buyers understand how the product connects to LinkedIn, how member permissions are granted and whether the workflow is built on LinkedIn-supported interfaces.
Does LinkedIn API approval mean LinkedIn endorses Ripply?
No. API approval is not an endorsement. It means the application has access to the relevant LinkedIn API programme and permissions.
Can LinkedIn API capabilities change?
Yes. LinkedIn versions its APIs and can change permissions, limits and programme requirements. That is why vendors should maintain supported integrations and be transparent about current capabilities.