Integration Requirements for Community Management

Warning

Deprecation Notice: The Marketing Version 202508 (Marketing August 2025) will be sunset on August 17, 2026. We recommend that you migrate to the latest versioned APIs to avoid disruptions. For information on all the supported versions, refer to the migrations documentation. If you haven’t yet migrated and have questions, submit a request on the LinkedIn Developer Support Portal.

LinkedIn is in the process of rolling out a Technical Sign Off process for the Community Management program. This ensures that our members get the best experience whether using LinkedIn's native UI or a partner product. The technical review and sign off also ensures that there are no gaps in integrations and that partner products keep up with the latest features and updates released by LinkedIn.

As an API partner, please go through the requirements listed below. These are the capabilities that an integrating partner is expected to build in their product. We request you to plan and incorporate these features early in your design. When you're nearing completion, you must initiate a Technical Sign Off request by contacting your LinkedIn POC on the Business Development team.

A demo will be scheduled during which you'll be asked to showcase all your product capabilities. During this evaluation, LinkedIn can suggest modifications which should be completed for the sign off. If all criteria are met (as per the envisioned scope), the technical sign-off is awarded.

Requirements

Rule	API capabilities to be demonstrated in Demo
	Basics
CM-001	Demonstrate OAuth 2.0 integration, with right scopes, consent screen.
CM-002	Demonstrate ability to periodically verify that an access token is valid (heartbeat /me).
CM-003	Demonstrate ability to detect access token expiry.
CM-004	Demonstrate ability to retrigger OAuth Flow in case token has expired or been invalidated.
CM-005	Demonstrate ability to use refresh tokens to mint new access tokens.
CM-006	Demonstrate ability to detect refresh token expiry and retrigger OAuth Flow.
	Organization Administration
CM-007	Demonstrate ability to retrieve all organizations for the authenticated organization admin.
CM-008	Demonstrate ability to retrieve organization information including organization logo for administered organizations.
CM-009	Demonstrate compliance with MDP data storage requirements.
CM-010	Demonstrate ability to retrieve access control information for an organization administered by the member.
	Managing Organic Company Page Posts
CM-011	Demonstrate ability to retrieve all posts for an administered organization.
CM-012	Demonstrate ability to retrieve organization posts by ID for all media categories (TEXT, ARTICLE, IMAGE, RICH, VIDEO, CAROUSEL).
CM-013	Demonstrate ability to create organic posts for an organization for at least two media category (TEXT, ARTICLE, IMAGE, RICH, VIDEO, CAROUSEL).
CM-014	Demonstrate ability to target organic posts.
CM-015	Demonstrate ability to retrieve likes, comments and nested comments for organization posts.
CM-016	Demonstrate ability to retrieve posts containing mentions along with its comments.
	Reporting
CM-017	Demonstrate ability to get number of followers for an organization. For more information, see Data Storage Requirements.
CM-018	Demonstrate ability to report on organization follower statistics. For more information, see Breaking Change Policy.
CM-019	Demonstrate ability to report on organization page statistics.
CM-020	Demonstrate ability to report on organization share statistics.
CM-021	Demonstrate ability to report on video statistics.
	Optimizing retrieval of updates using PULL Method
CM-021	Demonstrate ability to PULL Shares IDs in an optimized manner.
CM-022	Demonstrate ability to configure the intervals between PULL requests.
CM-023	Demonstrate ability to recover from outages using a time-bound PULL request.
	Optimizing retrieval of updates using PUSH Notifications
CM-024	Demonstrate ability to register webhooks for specific Company Pages.
CM-025	Demonstrate ability to register webhooks for specific Events.
CM-026	Demonstrate ability to register webhooks for @mentions usecase.
CM-027	Demonstrate ability to de-register webhooks when unsubscribed by user.
CM-028	Demonstrate ability to recover from outages, missed PUSH notifications.