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.
Migrating all applications to Member Permissions
In August 2012, we introduced Member Permissions. This feature allows you to specify exactly which information the member shares with your application and actions you can take on their behalf. In November 2012, we introduced a migration path to this new flow for applications created before that change. We have been thrilled to see the excitement in adopting Member Permissions and many of you are already using it to streamline your site registration.
Key benefits of this feature are as follows:
- Members have more visibility: LinkedIn members have clearer visibility into the data and actions your application requests access to.
- Standardized lifespan of access tokens: Previously members could choose to grant tokens ranging from one day to forever. Now all tokens are 60-days in length. Developers can proactively renew tokens in 60-day increments when members come back to their app.
- Ability to fetch additional profile data: You can fetch email address of the authenticated user, which wasn't previously available.
- Standardized profile data: You can continue to access the Full Profile of logged in member, however you can only retrieve the Basic Profile for users other than the authenticating member.
|LinkedIn Authentication screen before migration
||LinkedIn Authentication screen after migration
What does that mean for your current application?
If you are already using Member Permissions, you will not be impacted by this. Otherwise, once you migrate your application, your current access tokens will continue to be valid but will have a 60-day lifespan. When you renew these tokens or for first time users, the user will see our authorization dialog which details the member permissions that your application requests. Any subsequent renewals of the token will be seamless to the user as long as the permission scopes of your application haven't changed and the user is still logged into LinkedIn.
What if your application is not migrated by August 5th?
Starting July 16th, we will automatically migrate applications that are not already on the new flow. All your existing access tokens will be enabled for all scopes, except for email address. This mimics the behavior prior to the migration, with the exception that new data accessibility rules for connection profiles will be in effect and the expiration of access tokens will be set to 60-days.
We understand this migration requires some changes on your part, and our goal is to provide you with the lead time and support you need to be successful. We're excited to help enhance your application's user experience and help you make the most of what the LinkedIn Platform has to offer.