Linkedin – Community Management API: This API product requires that it be the only product on the application for legal and security reasons.

🧩 Why You See the Restriction

You’re seeing:

“This API product requires that it be the only product on the application for legal and security reasons.”

That means:

• Your LinkedIn app already has other products (like Share on LinkedIn, Sign in with LinkedIn, etc.).

• LinkedIn’s Community Management API belongs to a special tier that can’t coexist with those products.

• LinkedIn enforces this at the app level — only one app type can hold that API.

In other words:

🚫 If your app already has any other LinkedIn product enabled, you cannot add Community Management API to it.

---

✅ Why “Other Apps” Can Request It

Those “other apps” you’ve seen that have Community Management API access are:

1. Dedicated standalone apps created specifically for that API.
   (They have no other products added.)

2. Approved partners or vendors under LinkedIn’s “Marketing Developer Platform” (MDP) program.
   These developers went through LinkedIn’s review and partnership process.

So, those apps were either:

• created freshly, with only Community Management API selected, or

• belong to a LinkedIn partner organization with special privileges.

That’s why they can access it while your general-purpose Stackposts app can’t.

---

🧠 Example

---

✅ How You Can Enable It

You’ll need to create a new LinkedIn developer app dedicated to that API:

1. Go to https://www.linkedin.com/developers/apps

2. Click Create app

3. Give it a name like:
   👉 Stackposts LinkedIn Page Manager

4. Do not add any other product yet.

5. Click Request access for Community Management API

6. Fill in the use case — example below 👇

---

✍️ Example Use Case Text

You can paste this into the review form:

Our SaaS platform (Stackposts) enables verified business owners to connect and manage their LinkedIn Company Pages.
We use the Community Management API to publish posts, read analytics (impressions, clicks, engagement), and manage page interactions in compliance with LinkedIn’s policies.
No user data is shared or stored outside of authorized scopes.

---

🧩 After It’s Approved

Once LinkedIn approves your new app:

• Use its Client ID / Secret inside Stackposts’ LinkedIn integration settings for organization analytics & posting.

• Keep your old app for basic profile login (Sign in with LinkedIn) if needed.

Stackposts already supports linking multiple apps per platform (you can handle both).

 

—————————–

You’re currently in the LinkedIn Developer Portal → Products tab for your app named Stackposts Integration.

Let’s go over what this screen means and which products you actually need for Stackposts 👇

---

✅ Stackposts Only Needs These LinkedIn Products

To connect LinkedIn Pages, post content, and pull analytics, you only need:

---

⚠️ You DO NOT NEED These for Stackposts

---

🧩 About the Error You Saw Earlier

When you tried to request Marketing Developer Platform or Advertising API, LinkedIn showed:

“This API product requires that it be the only product on the application…”

That’s because those marketing-tier APIs (Advertising, Lead Sync, etc.) require a dedicated app.
You can’t mix them with “Share on LinkedIn” or “Sign In with LinkedIn”.

---

🧠 Recommended Setup for Stackposts Integration

Keep your current app as-is and use it for publishing + analytics.
Here’s what to do:

1. Keep Share on LinkedIn ✅

2. Optionally enable Sign In with LinkedIn

3. Request access to Community Management API (you’ll need to provide short info: “Used by Stackposts to manage company page posts and analytics.”)

That’s all Stackposts needs for:

• Connecting user LinkedIn profiles and organization pages

• Publishing posts

• Reading insights (impressions, engagement, followers, etc.)

---

✅ Final Summary