Making it easier for you to develop on LinkedIn
Today we announced updates to the LinkedIn Platform. In this post, learn more detailed technical overview of these changes, to help you understand how these changes will impact your code. Additionally, we have a few small new features to help you monitor and manage your application.
Streamlining Registration and Authentication
Developers can now request email addresses from users who want to use their LinkedIn credentials to sign-in and register for applications.
We've implemented this by introducing Member Permissions, a feature that allows you to specify exactly which information the member shares with your application and actions you can take on their behalf. And our redesigned Authentication screen displays to potential users the Member Permissions you've requested.
With Member Permissions, we have further refined how members control their profile information, along with the profiles of their connections. The profile is now broken into four pieces:
- Profile Overview: A digital business card with name, photo, headline, and current positions
- Email address: The member's primary email address on LinkedIn
- Contact Information: Address, phone number, and bound accounts
- Full Profile: Full profile including experience, education, skills, and recommendations
We encourage you to enable features in your applications that allow members to interact with and share to their network. The following permissions enable you to bring engagement features to your application:
- Network Updates: Retrieve and post updates to LinkedIn
- Connections: Read 1st and 2nd degree Connections
- Group Discussions: Retrieve and post group discussions
- Invitation and Messages: Send messages and invitations to connect
In situations where our APIs return profile information of members in your user's network, your application will now have access to fields within the Profile Overview Member Permission. We made this change to better balance the experience for all our members, whether they're using your application themselves or connected to those that are. For more information on profile fields available to your application, review our Profile Fields documentation.
Resources without member specific information, such as Companies and Jobs are not impacted by Member Permissions. You can continue to use them without needing to explicitly for permission.
On the technical side, we've borrowed the OAuth 2.0 concept of the "scope" parameter and incorporated it into our OAuth 1.0a and JS Authentication flows.
For API keys using Member Permissions, we have also standardized the duration of our access grants at 60 days, with the ability for you to seamless extend them in 60 days intervals whenever a member comes to your application.
Full details on Member Permissions and Access Grant Extensions are covered in our Authentication documentation.
Improving the Share Experience
With over 1 million publisher sites already enabling the ability to share content to LinkedIn, we're now making it even easier for our developer community to use LinkedIn as their main distribution platform for discussing and sharing professional content.
Our Share API now provides qualified developers with attribution on LinkedIn’s update stream, enabling greater rewards for building customized and integrated LinkedIn sharing experiences in your applications.
If you are interested in attribution, visit our Partner Programs page for eligibility criteria and the application process.
The richer the content shared on LinkedIn, the more engagement it creates among members. As developers using our Share API, you can always specify the exact title, description, and image that you want to be attached the the member's share.
Since some developers cannot incorporate this information into their API calls, we've updated how we process text-only updates. Now, when you only provide a Share without an URL or image, we will automatically identify embedded URLs in the status, and use that to provide a richer experience.
Read Share API best practices and technical details in our revised Share API documentation.
New Throttle Monitoring Dashboard
To help you understand your throttle limits, we have created a Throttle Monitoring Dashboard. For each resource, you can view your application and member limit, along with knowledge whether your application or members have hit today's quota.
Remember, we always return a Status Code of 403 whenever you are throttled. It is a best practice to catch and log this result, and have your application behave accordingly.
However, to simplify debugging, you can now use our dashboard to check the current status of your applications.
The Throttle Monitoring Dashboard is available in your API Key Management Console by clicking View API Usage.
We are excited to see how these features will enable your applications to be more effective than ever.