LinkedIn API V2：获取成员应用内连接权限及合作类型选择咨询

Let’s break this down clearly based on your specific use case:

First, let’s lock in the permission you actually need:

• r_network is the correct permission here (since r_compliance is reserved for compliance/audit-focused workflows, not general member connection retrieval).

Now, let’s map this to LinkedIn’s three partner programs to find the right fit:

1. Talent Solutions #

This program is built for recruitment, talent sourcing, and talent management use cases. If your app’s core purpose ties to hiring, candidate matching, or building talent pipelines (e.g., helping users connect with colleagues or potential candidates in their network who also use your app), this is the program you should apply for. The r_network permission is commonly approved here for talent-focused connection retrieval.

2. Marketing Solutions #

This program centers on brand marketing, content promotion, and audience engagement. Its permissions are geared toward social content analytics, ad targeting, and brand reach—not fetching member connections. This is not the right choice for your specific workflow.

3. Sales Solutions #

If your app is designed for sales lead generation, CRM integration, or B2B outreach, this program is the ideal pick. The r_network permission is regularly granted here for use cases like helping sales users prioritize outreach to their network contacts who also use your sales-focused tool.

Critical Tips for Approval #

When submitting your application, be explicit about:

• Exactly how you’ll use the connection data (e.g., "Matching users with other app members in their LinkedIn network for cross-team talent collaboration" or "Helping sales users identify high-priority network contacts who use our CRM platform").
• That you’re only accessing connections who also use your application (LinkedIn prioritizes data privacy, so this detail will strengthen your case significantly).

内容的提问来源于stack exchange，提问作者Muhammad Omar ElShourbagy