linkedin-api

Linkedin API Pulse Share

我的梦境 提交于 2019-12-05 21:25:11
I am trying to integrate my blog to Linkedin Pulse by connecting to my linkedin app. I found that posting to API /v1/people/~/shares shares my update but I can't figure out how to post it on Pulse - long post. Is it even possible? Cheers! Posting on Pulse is not available using LinkedIn's public API. And as far as I know, they are not offering this to their partners either. Managed to fix it with Curl. The tool is logging in to your linked in (user and password). Gathers the token and post to LinkedIn pulse, additional request is used to upload image and tags using post ID at that time. Cheers

Permissions to access Linked In privatePlayableStreams - 500 or 403 error

浪尽此生 提交于 2019-12-05 18:49:58
I have a next issue using Linked In API V2: curl -X GET --header 'Accet: application/json' --header 'Authorization: Bearer <my token>' 'https://api.linkedin.com/v2/adCreativesV2/62119114?projection=(variables(data(com.linkedin.ads.TextAdCreativeVariables(vectorImage~:privatePlayableStreams))))' | json_pp { "variables" : { "data" : { "com.linkedin.ads.TextAdCreativeVariables" : { "vectorImage" : "urn:li:digitalmediaAsset:C560EAQFjbUgC1TlCcw", "vectorImage!" : { "message" : "URN Resolution failed for unknown reasons.: com.linkedin.restligateway.exceptions.GatewayAccessException: Not enough

Linkedin V1 update-comments-as-company api throws 500 error code

前提是你 提交于 2019-12-05 18:35:44
We are using Linkedin v1 api update-comments-as-company endpoint to post comments on behalf of company page managed by the user. Nowadays this endpoint throws 500 error response while trying to add comment. Example request: curl -X POST -H "Authorization: Bearer xxxx" -H "Content-Type: application/json" -H "x-li-format: json" 'https://api.linkedin.com/v1/companies/12345/updates/key=UPDATE-c12345-640455667889990765/update-comments-as-company' --data '{"comment": "Posting as a company!"}' Response: { "errorCode": 0, "message": "Internal service error", "requestId": "OBVNKWRJDC", "status": 500,

How to Get Access Token Using LinkedIn API JavaScript SDK

喜欢而已 提交于 2019-12-05 15:28:28
I am trying to get LinkedIn Access Token after login. Login is working fine with JavaScript SDK and I'm able to receive "oauth_token" and member_id . I need access_token to verify the email address (if it is not forged on the way). Below is my script: <script> function LoginWithLinkedIn() { IN.User.authorize(afterAuthorization); } function afterAuthorization(response){ debugger if(IN.User.isAuthorized()==true){ getProfileData(); } } function onSuccess(data) { console.log(data); } function onError(error) { console.log(error); } function getProfileData(r) { IN.API.Profile("me") .fields("id

LinkedIn Login: Blocked a frame with origin “https://platform.linkedin.com” from accessing a frame with origin

心不动则不痛 提交于 2019-12-05 10:52:37
We had Login with LinkedIn code set up and working perfectly with LinkedIn Javascript SDK, where a few days ago we suddenly started to get this: Blocked a frame with origin "https://platform.linkedin.com" from accessing a frame with origin "https://OUR_SITE". Protocols, domains, and ports must match. And login does not complete (it returns from LinkedIn to our page and waits forever). I have no idea why we started to get this error when everything was working perfectly (we haven't changed a single line of code about the login mechanism, or allow origin headers/files, or LinkedIn settings etc)

Retrieve UGC Posts through LinkedIn V2 API got ClassCastException error

纵饮孤独 提交于 2019-12-05 09:19:43
I'm trying to retrieve a list of UGC posts by calling the following API https://api.linkedin.com/v2/ugcPosts?q=authors&authors=List%28urn%3Ali%3Aorganization%3A[ORG_ID]%29 [ORG_ID] is id of my organization. Then I got this error { "serviceErrorCode": 0, "message": "java.lang.ClassCastException: java.lang.String cannot be cast to com.linkedin.data.DataComplex", "status": 500 } I've already authorized to use API V2 and include X-Restli-Protocol-Version:2.0.0 in the header. I was having issues with this too, the parens on the authors query param shouldn't be encoded. I.e., try: https://api

Firebase Auth (with Custom Token, for Linkedin) returns a user with no email and no data (only uid)

冷暖自知 提交于 2019-12-04 20:54:07
I'm trying to login with Linkedin and Firebase. I generate on my server the custom token, I have my private key, I use RS256 and this is my payload: "iss" : service_account_email "sub" : service_account_email "aud", "https://identitytoolkit.googleapis.com/google.identity.identitytoolkit.v1.IdentityToolkit" "iat", Date().timeIntervalSince1970 "exp", Date().timeIntervalSince1970.advanced(by: 3600) "uid", String.randomString(length:28) I create the token, send it back to the app and from this I do: Auth.auth().signIn(withCustomToken: token!, completion: { (user, error) in I receive no error and a

Linkedin v2 api: Not enough permissions to access: GET /countriesV2

蹲街弑〆低调 提交于 2019-12-04 20:08:38
While fetching organization follower statistics using LinkedIn v2 API I used country projection to get country, region, industries, functions details also. But it throws error for countries alone, other details are included as expected. URN Resolution failed for unknown reasons.: com.linkedin.restligateway.exceptions.GatewayAccessException: Not enough permissions to access: GET /countriesV2 My query is curl "https://api.linkedin.com/v2/organizationalEntityFollowerStatistics?q=organizationalEntity&organizationalEntity=urn:li:organization:12345&projection=(elements*(*,followerCountsByRegion*(*

No large images in shares posted using LinkedIn API

自古美人都是妖i 提交于 2019-12-04 18:55:58
During last couple of weeks any shares made using LinkedIn sharing API don't display large images, though we provide all required information for this, including image URL. The same happens when we use REST Console . Below you can see a sample request and how the share looks like. { "comment": "How Triggre achieves its simplicity", "content": { "title": "Triggre / Blog / Design Philosophy - Part 3", "description": "In the previous two posts about our design philosophy you could read how we decided to build Triggre and why we chose simplicity as the core of our desi...", "submitted-url": "https