-
How can I get access LinkedIn member data?
You can use Sign In with LinkedIn to get basic member profile data.
If you’re looking additional member information, it can be made available to authorized LinkedIn partner developers via our Partner Program.
Where can I find my API key?
Click on the My Apps link in the top navigation menu to manage your LinkedIn applications.
From here, you can create a new application if you don't already have one or view the details of your existing applications. You will find your Client ID (otherwise known as API Key/ID or Consumer Key/ID) listed in the "Authentication" side nav link, underneath the header "Authentication Keys".
Can I reset my application's Client Secret value?
At this time, LinkedIn does not have the tools available for you to generate a new Client Secret value. If you require a new value, please create a new set of application credentials.
How can I find out how many calls have been made by my application today?
You can find API usage information by clicking on the My Apps link on the top navigation menu.
Click on the "Usage & Limits" side nav link associated with your application to see your daily usage. Remember that the daily statistics reset at midnight UTC.
-
How can I tell LinkedIn's APIs to send responses in JSON format?
By default, LinkedIn's APIs send responses back in XML format. If you would like to receive data in JSON format, you can do so using either one of the two following options:
- Add a format=json URL parameter to your REST endpoint (e.g. https://api.linkedin.com/v1/people/~?format=json).
- Include a x-li-format: json HTTP header with your request.
- Add a format=json URL parameter to your REST endpoint (e.g. https://api.linkedin.com/v1/people/~?format=json).
-
Why do I see an "Error: You must specify a valid JavaScript API Domain as part of this key's configuration." error in my JavaScript console?
For security reasons, you must configure the domain names that your LinkedIn JavaScript SDK enabled application is allowed to run on in your application's configuration.
-
Is it possible to request an OAuth 2.0 access token that lasts longer than 60 days?
No, LinkedIn will only provide you access tokens that last 60 days. If your application is properly built to refresh the user's token prior to its expiry date, this limit should not cause you any problems. Refreshing an access token can be done silently behind-the-scenes and should have no impact on user experience.
How do I refresh my access token?
Please consult the Authenticating with OAuth 2.0 guide for instructions on refreshing your access tokens.
Can I have a variable OAuth 2.0 redirect uri values?
While it is possible to specify more than one allowable redirect uri value in your application's configuration, OAuth 2.0's best practice security guidelines do not allow the use of wildcard values.
Also note that any URL arguments or internal anchors (i.e. #foo) in redirect uris are ignored, so it is not possible to achieve a wildcard effect through their use.
Why do I see an "Invalid redirect_uri. This value must match a URL registered with the API Key." error?
If your application encounters an "Invalid redirect_uri. This value must match a URL registered with the API Key." error message during the authentication process, there are two possible things that may be wrong:
- You did not register your OAuth 2.0 callback URL in your application's configuration.
- The value of your redirect_uri argument in your OAuth 2.0 authorization request does not match any of the registered callback URL values in your application's configuration.
Can I get an access token for my application that doesn't require a member to login?
We do not provide access tokens for applications that are not associated with a particular LinkedIn member.
If your application requires you to make API calls in an automated way - without user interaction, you need to bootstrap the first access token request by manually signing in, and then ensure that your application refreshes the token automatically prior to expiry to avoid the need for additional human authentication.
Is OAuth 1.0a no longer supported?
While we have not announced the official deprecation of OAuth 1.0a in conjunction with LinkedIn's APIs, we no longer actively encourage or support its use.
Existing applications built with OAuth 1.0a will continue to functional normally until such time as we officially announce its sunset.
Using or transitioning to OAuth 2.0 is strongly encouraged for all applications.
-
Where can I find LinkedIn plugins to use on my website?
Links to relevant plugins can be found in the documentation related to Sign In, Share and Manage Company Pages - however there is also a complete list of available plugins.
Why doesn't my plugin work on iOS 5.0+ devices?
LinkedIn's JavaScript SDK is incompatible with the way JavaScript is executed in versions of iOS greater than v5.0. There is no available work-around at this time.
If you need to ensure your integrations function reliably in environments that include iOS-based devices, you should rely on server-side REST calls rather than the JavaScript SDK.
Frequently Asked Questions