Is the only way to access r_fullprofile by applying for LinkedIn partnership after the new API policy?
My application is currently using it for fetching the users "Skills" which requires r_fullprofile instead of r_basicprofile.
Would I need to do any changes regarding the new policy if I only used r_basicprofile?
As per LinkedIn's documentation, "skills" fields are only available under the r_fullprofile member permission (https://developer.linkedin.com/docs/fields/full-profile) when making an API call to request member data.
After May 12th, 2015, apps will no longer be able to request this member permission without being specifically reviewed by LinkedIn for compliance with the Apply with LinkedIn use case (https://developer.linkedin.com/docs/apply-with-linkedin) or some other partnership program membership which grants access to that permissions.
Starting from May 12, 2015, Linkedin has limited the open APIs.
Access to r_fullprofile requires that you apply for and are granted access to this information from LinkedIn.
WHAT YOU NEED TO DO :
Apply for partner status with LinkedIn (Apply with Linkedin), explaining what your integration is and how it works. If it meets their criteria, then you will get access to those endpoints, but only for that app.
Member profile fields
The following selection of profile fields are available to all LinkedIn developers:
- Basic Profile Fields
- Location Fields
- Position Fields
Member profile fields available to Apply with LinkedIn developers:
The following selection of profile fields are only available to applications that have applied and been approved for the Apply with LinkedIn use case:
- Full Profile Fields
- Contact Info Fields
- Company Fields
- Publication Fields
- Patent Fields
- Language Fields
- Skill Fields
- Certification Fields
- Course Fields
- Education Fields
- Volunteer Fields
Check out this linkedin page for more details on which fields are available to all the developers and which are not.
来源：https://stackoverflow.com/questions/29279057/accessing-r-fullprofile-after-new-linkedin-api-policy-changes