I'm facing problems with my client because I can't get the share's statistics for his organization.
Since December 2021 the API is returning Internal Server Error for many request in the organizationalEntityShareStatistics endpoint.
API analytics
The request works for other organizations.
I have tried reaching Linkedin through their support pages but they have told me to post it here on stack overflow; In this private support request I show the app tokens used: https://linkedin.zendesk.com/hc/en-us/requests/26241?page=1 or here: https://www.linkedin.com/help/linkedin/cases/39424961
LinkedIn answered me that I should filter some posts, according to their "lifecycleState" field, which for some cases make the request fail, they should only be PUBLISHED or PUBLISHED_EDITED
Related
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.
What is the Github HTTP request limit?
I made a crawler to crawl data from Github, but sometimes it returns with error code 429 which is "Too many request", so I would like to know what is the Github request limit per minute or per hour?
The rate limits are based on the token (pat, oauth, app, deploy key) that you are using and the value varies based on the kind of license (free, pro, team, Enterprise) your account falls under and she kind of API you are accessing (public API, private API, Rest or GraphQL)
The docs for rate limits can be found here:
https://docs.github.com/en/rest/overview/resources-in-the-rest-api#rate-limiting
https://docs.github.com/en/rest/reference/rate-limit
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.
While using Share Api i got response as follows
{
"serviceErrorCode": 100,
"message": "Not enough permissions to access: POST /shares",
"status": 403
}
this is due to the fact that for the linkedin V2 API you need to become an linkedin partner. this can take up to a month befor you get a response.
Partnering with LinkedIn provides you with additional API functionality & data access, increased call limits & dedicated support. Read more about our various Partner Programs and use cases and see if one is a match for your app. Applications are only accepted when we feel that they're providing value to members, developers and LinkedIn.
for more information see this link :
https://developer.linkedin.com/partner-programs
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