Share via

Community Management App Review

  • Article

Warning

Deprecation Notice
The Marketing Version 202310 (Marketing October 2023) and earlier versions (excluding 202306 and 202307) have been sunset. Additionally, the unversioned APIs will be sunset soon. We recommend that you migrate to the versioned APIs as well as migrate to the new Content and Community Management APIs to avoid disruptions. See the Migration page for more details. If you haven’t yet migrated and have questions, submit a request on the LinkedIn Developer Support Portal.

To access the Community Management APIs, every developer must complete an access request form(s) which LinkedIn will review and vet the developer and app to ensure the APIs will be used in accordance with our API terms and supported use cases. Before submitting any access request, read the information below to understand the vetting process and requirements.

Before You Submit the Access Request

  • Read the LinkedIn Marketing API Terms and developer documentation.
  • Review our API and data restrictions to ensure your use case is supported and your application will not be rejected due to a restricted use case.
  • At this time, our Community Management APIs are only available to registered legal organizations for commercial use cases only.
  • Be prepared to share your business email address and your organization’s legal name, registered address, website, and privacy policy. Your business email address will have to be verified. If you don’t receive the verification email, be sure to check your email's spam folder, junk folder, social tab, and promotional tab. Personal email addresses will not pass the vetting process.
  • Ensure a super admin of the LinkedIn Page associated with your organization has verified your application.
  • Ensure that your application does not include any portion of the LinkedIn or Microsoft names or logos (e.g. Linked or In).
  • Ensure that you have filled out all required fields in the access request form accurately and completely.

Requirements for Standard Tier Upgrade Only

  • Make sure your application has been approved for the development tier and you have fully integrated the Community Management APIs into your application. Subsequent changes to your application's functionality after your application has been reviewed by LinkedIn may require re-review.
  • Prepare to provide a company and product overview, description of your use case, and test credentials for our reviewers to review your application.
  • Prepare a screen recording/ screencast of your application that demonstrates each use case that you specified in the access request form (additional details are included below):
  • Ensure the screen recording is high resolution and downloadable.
  • Please limit your screencast to just the screens associated with your application (i.e. close all other windows and applications before recording).
  • Narration is recommended.

Note

Any failure to complete the above tasks may result in your access request being rejected.

Application Review for Community Management API Access

Development Tier Access

Once you have created your application and submitted the access request form, your access request form will be reviewed by LinkedIn for the following:

  • Approved use case
  • Verified business email address
  • Verified organization
  • Verified organization website and domain address
  • Application verified by LinkedIn Page associated with same organization

If your application is reviewed and approved, you will get Community Management Development tier access.

If your application is rejected, review the qualifications, create a new app, and submit a new Development tier access request form. You will not be able to re-apply for Development tier access with your existing app.

Standard Tier Access

Once you meet the above requirements for access to the Development tier, you will find a Standard tier access request form in the Developer Portal under My Apps > Products. To get access to Standard tier, you will be required to complete this access request form and submit a screen recording of your app. Your application and access request form will be reviewed for the following:

  • Approved use case
  • Valid privacy policy
  • Compliance with our terms, restrictions, security, privacy, and trust requirements, and data storage requirements
  • Screen recording that accurately demonstrates all core functionality as outlined above

If you are approved for Standard tier and would like to apply your Standard tier access to a different app, you will need to complete another Standard tier access form for the app and in the form indicate you have an existing app with Standard tier access. You will be prompted to provide the client ID for the approved Standard tier app. This will expedite the review process.

If your application is rejected, review the qualifications, create a new app, and submit a new Development tier access form. You will not be able to re-apply for Standard tier access with your existing app.

Screencast requirements

  • Ensure the screen recording is high resolution and downloadable.
  • Please limit your screencast to just the screens associated with your application (i.e. close all other windows and applications before recording).
  • Narration is recommended. Our reviewers should be able to readily understand what you’re demonstrating.
  • Prepare a screen recording/screencast of your application that demonstrates the following test cases for each use case that you specified in the access request form for access to the Standard tier.

For Page Management Use Cases

  1. Demonstrate an application user approving access to their LinkedIn page data via the complete OAuth flow.
  2. Demonstrate a user posting to their LinkedIn page via your app.
  3. Demonstrate how a comment on that post by a member* is displayed to users in your app.
  4. Demonstrate what personal data fields from the commenter’s LinkedIn profile are displayed to users in your app.
  5. Demonstrate any other core functionality that uses member* personal data from LinkedIn (e.g. profile data, content of posts or comments, etc.).

For Brand Engagement Use Cases

If you don’t have a Page Management use case, demonstrate the following for your Brand Engagement use case:

  1. Demonstrate an application user approving access to their LinkedIn page data via the complete OAuth flow.
  2. Demonstrate how a mention of the user’s LinkedIn page in a post by a member* is displayed to users in your app.
  3. Demonstrate what personal data fields from the mentioning member’s LinkedIn profile are displayed to users in your app.
  4. Demonstrate any other core functionality that uses member* personal data from LinkedIn (e.g. profile data, content of posts or comments, etc.).

For Page Analytics Use Cases

  1. Demonstrate an application user approving access to their LinkedIn page data via the complete OAuth flow (if not already demonstrated via one of the preceding use cases).
  2. Demonstrate how the performance of the page’s posts (e.g. number of reactions) is displayed to users in your app.
  3. Demonstrate what personal data fields from the LinkedIn profiles of members* who engage with the page’s posts are displayed to users in your app (if not already demonstrated via one of the preceding use cases).
  4. Demonstrate any other core functionality that uses member* personal data from LinkedIn (e.g. profile data, content of posts or comments, etc.).

For Executive Management Use Cases

  1. Demonstrate an application user approving access to their LinkedIn profile data via the complete OAuth flow.
  2. Demonstrate a user posting to their LinkedIn profile via your app.
  3. Demonstrate how a comment on that post by another member* is displayed to users in your app.
  4. Demonstrate what personal data fields from the commenter’s LinkedIn profile are displayed to users in your app.
  5. Demonstrate any other core functionality that uses member* personal data from LinkedIn (e.g. profile data, content of posts or comments, etc.).

For Employee Advocacy Use Cases

  1. Demonstrate an application user approving access to their LinkedIn profile data via the complete OAuth flow.
  2. Demonstrate a user posting to their LinkedIn profile via your app.
  3. Demonstrate how a comment on that post by another member* is displayed to users in your app.
  4. Demonstrate what personal data fields from the commenter’s LinkedIn profile are displayed to users in your app.
  5. Demonstrate how aggregate engagement on the post is displayed to users.
  6. Demonstrate any other core functionality that uses member* personal data from LinkedIn (e.g. profile data, content of posts or comments, etc.).

Note

*A member is an individual that has registered and joined the LinkedIn Network.

If your application doesn’t include certain functionality specified in the above test cases, please just note that in your recording.

Please note that even if LinkedIn approves your integration, you are solely responsible for ensuring that your integration (including all use, disclosure, and storage of LinkedIn data) is, at all times, in compliance with: (a) the LinkedIn Marketing API Terms and the LinkedIn developer documentation; and (b) all other requirements or restrictions that LinkedIn separately communicates to you (e.g. during or after the vetting process). LinkedIn retains the right to monitor your application and suspend or discontinue access to the Community Management APIs for any non-compliance with the LinkedIn Marketing API Terms, even if your application was previously approved by LinkedIn.