we are aware of the issue and are working to restore service as soon as possible sorry, our API is experiencing intermittent issues
we are aware of the issue and are working to restore service as soon as possible sorry, our API is experiencing a limited-scope problem
please see this thread for updates sorry, the developer portal is currently undergoing scheduled maintenance
service is expected to be restored around 09:00PM PST OAuth 2.0 Authorization issues?
As previously announced, LinkedIn is now enforcing redirect URLs rule for OAuth 2.0 applications: More information. If you have any questions, please post to this thread in our forums: Thread for questions OAuth 2.0 Extension
LinkedIn is extending a courtesy brief period for developers to update their OAuth 2.0 redirect URLs.
If you have any questions, please post to this thread in our forums: Thread for questions. OAuth 2.0 Redirection URL
Beginning Monday April 28, 2014, LinkedIn's APIs will begin enforcing OAuth 2.0 redirect URLs.
If you have any questions, please post to this thread in our forums: Thread for questions. On July 21st between 4pm and 7pm PST we will be performing platform maintenance. You may see limited performance issues during this time. We apologize for any inconveniences generated by any service interruptions. We will be performing site wide maintenance on October 10th between 8 pm and 11 pm PST. This maintenance applies to all LinkedIn sites and applications, including our APIs. You may experience limited availability of certain APIs during this time. We apologize for any inconvenience this may cause. Please don't hesitate to reach out on our forums if you continue to experience API availability issues after the maintenance window In light of the recent disclosure of the "Poodle" SSL vulnerability, LinkedIn is joining the large number of services that have actively removed support for SSLv3, effective immediately. If you are experiencing errors related to HTTPS-based communication with our APIs, please ensure you are using a client/library that supports TLS 1.0+ instead of SSLv3 to avoid disruption. Attention, developers! We have transitioned to StackOverflow for forum-based support. Learn more about this change.
LinkedIn Platform Launches OAuth 2.0
At LinkedIn, one of our three key product goals is simplicity. Unfortunately, many developers have found OAuth 1.0a to be anything but simple. While secure, it has some complexities that can make it difficult for developers to successfully create applications on the LinkedIn Platform.
We've heard from our community about their interest in OAuth 2.0, and we have wanted to provide it to you for a long time. After careful evaluation and analysis over the current state of the OAuth 2.0 specification, we now feel confident that OAuth 2.0 is sufficiently mature. That's why we're happy to announce OAuth 2.0 for LinkedIn APIs.
With support of our new authentication flow, you can focus on learning our APIs instead of struggling with authorizing your users.
What you'll get with OAuth 2.0:
- Simplified authorization without the added overhead of the traditional OAuth 1.0a "dance," greatly reducing complexity
- Easier ability to request member permissions when authorizing. Gone are the days of struggling with OAuth libraries that can't properly pass scope parameters
- Removal of the requirement to generate complex signatures with SSL
Technical details and code samples to help you quickly get started with OAuth 2.0 can be found in our Authentication document
For current developers interested in migrating, the document also details how the authentication flow is handled for your customers when moving from an existing OAuth 1.0a implementation to the new OAuth 2.0 flow. Of course, if you're happy with your current OAuth 1.0a solution, you're welcome to keep using it.
With OAuth 2.0, making authenticated calls to the LinkedIn APIs will be much simpler – all with less code.