How to Access LinkedIn Profile, Company, and Job Data
Match sign-in, company analytics, and recruiting tasks to the right LinkedIn access path, then integrate only the fields your workflow needs.
When you are connecting LinkedIn data to a CRM, company report, or recruiting system, write down the fields you need and who can authorize access. Member profiles, organizations, and jobs use different access paths. A publicly visible page or a successful LinkedIn sign-in does not grant permission for bulk collection or redistribution.
Steps
- 1
Map each field to its purpose and source
A sign-in flow may need only a member identifier and basic profile fields. A company page report should start with the team that manages that page. For jobs, decide whether you want to read your own listings, run a recruiting workflow, or receive a licensed feed. Treat those uses as separate entries in your access checklist.
- 2
Obtain access through the right API product
Check the API products approved for your app in the LinkedIn Developer Portal. For member sign-in, use OpenID Connect and request profile fields the user has authorized. Ask for email only if the workflow needs it. Access to organization and recruiting resources depends on the API product, the caller's role, and the agreement attached to it.
- 3
Test the smallest integration first
Read a few records with an authorized test account or organization. Check how the app handles missing fields and record the source, purpose, and update time. When a request returns 401 or 403, inspect the authorization, app product, and caller's role before making another request.
For a CRM sync, use the permitted stable identifier to match existing contacts. Store only the fields the source allows. Agree on a retention period and on what happens when a user revokes consent.
Frequently asked questions
Does LinkedIn sign-in give my app access to every profile?
It shares approved information for the member who signs in and consents. Other profile, organization, and job data require the access path defined for that API product.
What if my app lacks the API product I need?
Use a permitted export from your organization or a provider whose agreement covers the fields, use case, and redistribution rights you need.
References
Sign In with LinkedIn using OpenID Connect