如何获取LinkedIn其他成员资料？受限访问API相关疑问

Great question—this is a super common pain point with LinkedIn's API ecosystem, since their access model for member data is tightly locked down to protect user privacy. Let me break this down clearly for you:

First: What Are the "Restricted Access APIs"? #

These are API endpoints that don’t come with default access when you create a standard LinkedIn developer app. They require manual approval from LinkedIn, and access is only granted for specific, compliant use cases. For getting other members’ Person IDs, the key ones are:

• Member Search API: This is the primary tool for finding and retrieving Person IDs for members matching criteria like keywords, job titles, or company affiliations. It’s restricted because it lets you access data for members who haven’t explicitly authorized your app. The number of results and fields you can access will be limited based on your approved use case.
• Organization Access API (Enterprise Use Cases): If your app is built for an enterprise (e.g., internal HR tools, company talent platforms), this API lets you fetch Person IDs for members associated with a specific organization. Again, this requires enterprise-level approval and strict adherence to LinkedIn’s data policies.
• Connections API (Limited Scope): While not fully "restricted" in the same way, to get Person IDs for a user’s direct connections, you need the r_contactinfo or w_member_social OAuth permissions. But if you need IDs beyond the user’s immediate network, you’ll need the broader restricted access mentioned above.

How to Actually Use These APIs (Step-by-Step) #

1. Set Up a LinkedIn Developer App: First, create an app in the LinkedIn Developer Portal, complete all required verification steps (like domain validation and a public privacy policy page—this is non-negotiable for approval).
2. Apply for Restricted Permissions: Navigate to your app’s "Products" tab, find the restricted product you need (e.g., "Member Search"), and submit an access request. Be extremely specific here: explain exactly what your app does, how you’ll use the Person IDs, and how you’ll protect user privacy. LinkedIn manually reviews these requests, so vague applications will get rejected.
3. Authenticate & Call the API: Once approved, use OAuth 2.0 to get a valid access token. For example, a basic Member Search API call would look like this (replace placeholders with your token and search criteria):

   GET https://api.linkedin.com/v2/people-search?q=keyword&keywords=senior%20data%20analyst&count=15
   Authorization: Bearer YOUR_ACCESS_TOKEN
   

   The response will include a id field for each matching member—that’s the Person ID you need.
4. Respect Privacy & Limits: Even with access, LinkedIn will automatically block data for members who have set their profiles to private. You also can’t use the data for unauthorized marketing, scraping, or any purpose not outlined in your approval request.

Critical Notes to Remember #

• Approval Isn’t Guaranteed: LinkedIn is strict about who gets restricted access. Personal projects or apps with unclear use cases rarely get approved—this is mostly for enterprise tools, legitimate recruitment platforms, or services that provide clear value to LinkedIn members.
• Privacy First: You can’t bypass a member’s privacy settings, no matter what permissions you have. The API will simply omit data for members who’ve opted out of public visibility.

内容的提问来源于stack exchange，提问作者Levissie