LinkedIn is the world's largest business social networking hub. Launched in 2003, LinkedIn has millions of users and is implemented in over 200 countries. One purpose of the site is to allow registered users to maintain a list of contact details of people with whom they have some level of relationship, called Connections. Users can invite anyone (whether a site user or not) to become a connection.
The LinkedIn API is a RESTful platform that provides a simple, consistent representation of people, companies, jobs, and the interactions and relationships between them. Our query language lets you read data in XML and JSON at the granularity and aggregation that you choose. Use OAuth 1.0a to authorize users and begin making REST API calls using any programming language.The API’s access is restricted to authorized developers.
At the end of last year, LinkedIn announced major changes to its APIs and developer program. Those changes will soon take effect, and developers need to migrate accordingly by March 1. New developer program features, version 2 of its API, and the use of OAuth 2.0 will all be requirements on March 1.
As part of our series on the end of the API economy as we know it, we offer a story about a company that survived being shut out of the API that was the lifeblood of its business. This is the story of PeopleLinx, a company that made money using the LinkedIn API, until the API access was removed.
As various services like Facebook deal with competitors by packing more functionality into their apps, those apps are increasingly experiencing usability issues. In the old days of the API economy, outside developers could leverage a service's APIs to build something better. But those days are gone.