How will LinkedIn's changes to API Access affect us?
-
Below is a quote from an email from LinkedIn regarding changes to their API Access. How will these changes affect our use of this plugin? What will we need to do?
In an effort to provide the most value to our members, developers and to LinkedIn, we’re restricting our open APIs and providing further clarity about the specific use cases we’ll support. Starting on May 12, 2015, the following uses will be supported:
– Allowing members to represent their professional identity via their LinkedIn profile using our Profile API.
– Enabling members to post certifications directly to their LinkedIn profile with our Add to Profile tools.
– Enabling members to share professional content to their LinkedIn network from across the web leveraging our Share API.
– Enabling companies to share professional content to LinkedIn with our Company API.
By May 12, all new and existing applications must focus on at least one of the use cases above and adhere to our updated API Terms of Use in order to access our open APIs. All other APIs will require developers to become a member of one of our partnership programs.
- The topic ‘How will LinkedIn's changes to API Access affect us?’ is closed to new replies.
