"r_member_social" scope permission in Linkedin API

Question

I have created a Linkedin App on Linkedin developer portal and added the community management API product. But I couldn't find r_member_social scope among all products listed in developer portal.

I used the following API endpoint to get personal (member) posts and metrics.

• https://api.linkedin.com/rest/posts?q=author&author=urn%3Ali%3Aperson%3A6mkPA32Al
• X-Restli-Protocol-Version: 2.0.0
• Linkedin-Version: 202509
• Bear Token: AQWZTIrK08DX2vNq7BAXB7qxzx3IIWhAG ... (It is correct and working for other API endpoints)

If I call this endpoint without 'r_member_social' scope, it returns the response like the following.

{
 "message": "Member permissions must be used when using member as author",
 "status": 400
}

I think this is the permission issue. I am not sure how I can get this permission.

Link1. Linkedin Reference Link: https://learn.microsoft.com/en-us/linkedin/marketing/community-management/shares/posts-api?view=li-lms-2025-09&tabs=http#batch-get-posts

above link screenshot

enter image description here

It shows the image.

Link2. Also another link says that it is a closed permission we can't access. https://learn.microsoft.com/en-us/linkedin/marketing/lms-faq?view=li-lms-2025-08

above link screenshot

enter image description here

As you can check from above two links and screenshots, While API lists of Sep 2025 (Link1) show the API endpoints with 'r_member_social' scope,the Linkedin API FAQ of Aug 2025 tells it is a closed permission.

How can I use this API endpoint? Do I need the standard tier, not developer app? Or is it impossible to access the API?

I have tried to get posts and metrics of company members to measure the performance and future improvement.

• C3roe: "While API lists of Sep 2025(Link1) show the API endpoints with 'r_member_social' scope,the Linkedin API FAQ of Aug 2025 tells it is a closed permission." - The two aren't mutually exclusive.

Answer 1

It is currently impossible to access r_member_social. As you already noted, it requires additional permissions, but they are not currently accepting any requests to use it because of resource constraints (also written elsewhere in their documentation).

As a result, the only way to gain access is to apply when they begin accepting requests again.