I have been looking into de LinkedIn Compliance API, since our goal is to:
Allow users to send connection requests / "invitations"
Send chat messages to existing connections
Get the conversation history with a connection
But, as it seems, the API could be closed for new connections... While it is not mentioned in the docs of the Compliance API itself, or in its changelog, it is said to be "closed" on this page. Also, when trying to start a new application integration within the LinkedIn developer platform, it is not listed as an option.
So my question is twofold:
Is it still possible to connection to the LinkedIn Compliance API? (after being authorized, of course)
If not: could above three aims be achieved through another API? I have been browsing many of the docs, but was not able to find a substitute LinkedIn solution yet.
Related
I am currently using a linkedin API with r_lightprofile in my application.
Two months ago, I sent a request for access to r_fullprofile using the Partner Program form.
https://business.linkedin.com/marketing-solutions/contact-us
http://prntscr.com/opfnpd
I also sent a request to the Marketing Developer Platform, but the request is still pending (http://prntscr.com/opfvfx)
After all this, I got an email with a form to fill out information about the company.
But after filling out the form, I did not receive an answer that the company is suitable or not suitable for full access.
1) How long does it usually take to get access?
2) Does the linkedin API have support? Email, Live chat or something else?
3) Have I done everything for access? Maybe I missed something?
4) Does Linkedin send an email in case of failure?
It's been a long way for me too, I'll give you some random tips:
Make sure your app is connected to a LinkedIn company page and that the status is Verified. To do this, from the app dashboard, add to the Team members an administrator of the LinkedIn company page (as Admin member) and let him access the app dashboard. He should be able to see a Verify button to confirm the authenticity of the app.
The only support that was really helpful to me was Zendesk.
I'm having intermittent issues with signing in to LinkedIn with the LinkedIn Sign In API.
By intermittent I mean, I have two LinkedIn accounts, and as of this week one of them is unable to use the API to sign in to external services, such as the LinkedIn application I develop.
I'm authenticating via Auth0, whose engineers have confirmed there is an issue:
Over the last few weeks, the current version of the LinkedIn API for
sign-in has been intermittently failing when fetching the user
profile, causing a small number of users to fail to log in. The cause
of this issue is currently unknown, and is coming from LinkedIn
directly.
https://community.auth0.com/t/linkedin-connection-deprecated/20484/18
The Auth0 response i'm getting is the following (I've replaced senstivie response values with 'XX'):
{"name":"a0.response.invalid","message":"unknown error","json":{"error":"invalid_request","error_description":"InternalOAuthError: failed to fetch user profile (status: 500 data: {\n \"errorCode\": 0,\n \"message\": \"Internal API server error\",\n \"requestId\": \"XX\",\n \"status\": 500,\n \"timestamp\": 1550474289966\n})","state":"XX"},"status":0}
I know this API is being depreciated in March, but it's imperative that this API continues to work until the decommission date. I'm wondering if anyone has found a work around or solution to this issue, as it's impacting my ability to run real-world trials of my application scheduled in this week.
I've contacted LinkedIn support who directed me here.
Auth0 recently released a change to LinkedIn social connection, allowing you to use the new LinkedIn API (Version 2). You can change this by going to Connections-->Social-->LinkedIn-->Strategy Version dropdown and select Version 2. This should fix most of the login issues with the old deprecated version of LinkedIn API. More information post.
I've looked at all the questions and replies here and also applied for a partner account as the LinkedIn docs are so confusing now.
Where do I go to read about how to connect my API to give access to your or anyone's LinkedIn connections? I'd like to retrieve all a persons contact details and their connections details for populating an address book.
I got declined with no helpful info or pointers and getting in contact with LinkedIn is just as hard:
Dear developer,
Thanks for submitting your request for enhanced API access through the LinkedIn developer site. We reviewed the information provided in your application and determined that your use case does not qualify for enhanced API access.
Due to the high volume of requests we receive, we unfortunately cannot provide detailed feedback about your individual application. If you have further questions about the use cases we support through our Open APIs, please review our developer site (https://developer.linkedin.com/) and API Terms of Use (https://developer.linkedin.com/legal/api-terms-of-use).
Thanks for being part of our developer community.
The LinkedIn Business Development Team
[Please do not reply to this email]
I inherited a program that was written with the old LinkedIn API, and I'm trying to migrate it to the new API. When I try to get the r_basicprofile permission, my oauth token works. However, when I try r_network or rw_nus, I get a response
invalid scope -- your application has not been authorized for
r_network.
Yet, when I go to www.linkedin.com/developer/apps/xxxx/auth, the boxes for r_network and rw_nus are checked.
I.e., A request to
https://www.linkedin.com/uas/oauth2/authorization?response_type=code&client_id=xxxxxx&scope=r_basicprofile&state=yyyy&redirect_uri=http%3A%2F%2Fkalatublog.com%2Fwp-content%2Fmu-plugins%2Fimb-en%2Fhelpers%2Fsocial-connect%2Fapi%2Ffinalize.php%3Fapi%3Dlinkedin%26ch%zzzzz
works, but a request to
https://www.linkedin.com/uas/oauth2/authorization?response_type=code&client_id=xxxxxx&scope=r_network&state=yyyy&redirect_uri=http%3A%2F%2Fkalatublog.com%2Fwp-content%2Fmu-plugins%2Fimb-en%2Fhelpers%2Fsocial-connect%2Fapi%2Ffinalize.php%3Fapi%3Dlinkedin%26ch%zzzzz
gives that error. What am I doing wrong?
As of May 15,
After the grace period expires, several REST API endpoints will no longer be available for general use. The following endpoints are the only ones that will remain available for use:
Profile API — /v1/people/~ `
Share API — /v1/people/~/shares
Companies API — /v1/companies/{id}
If your application is currently using any other API services (e.g. Connections, Groups, People Search, Invitation, Job Search, etc.) you will have to apply to become a member of a relevant Partner Program that provides the necessary API access to continue to leverage any of the endpoints that are not listed above.
It looks like linkedin no longer wants to share anything with their API. Creating a new app indicates that the only possible options are r_basicprofile, r_emailaddress, rw_company_admin, and w_share:
TLDR: they have locked down the API and restricted the usage to an extremely limited set of access points.
I did some more digging. The linkedin website is misleading. On my app linkedin page, it says that I'm approved for rw_nus and r_network, but on this page
https://developer.linkedin.com/support/developer-program-transition
it says those are no longer approved.
So the app home page in linkedin incorrectly said I had those permissions.
Heres the link if you want to Apply for Linkedin
https://help.linkedin.com/app/ask/path/api-dvr
I'm working on updates of exisitng iOS app which uses LinkedIn REST API.
Earlier to get posts of user I made request to https://api.linkedin.com/v1/people/{id}/network/updates?format=json
I need to get r_network permission to accomplish that. But now with changes in API that request doesn't work. I couldn't find any useful info in Developer Program Transition Guide nor in developer docs.
According to the transition guide, there are only 3 endpoints that are generally available:
Profile API — /v1/people/~
Share API — /v1/people/~/shares
Companies API — /v1/companies/{id}
Your request is clearly not one of these endpoints. If you have not begun a discussion with people in the partnership program, you should start that process now.