Hi Carlos,
I was testing and trying to find out the reason of demo not working and discovered that ProfileCurrentMember failes with 404 error and message from LinkedIn:
"Could not find person based on: ~%3A%28id%2Cformatted-name%2Cpicture-url%2Clocation%2Cindustry%2Cheadline%2Cpublic-profile-url%29"
The endpoint is
and stack is
I think that it may be related to URL encoding as when I try to call basic info API https://api.linkedin.com/v1/people/~?format=json it works fine but as soon as I add profile fields I start having this error. Ifhttps://api.linkedin.com/v1/people/~:(id,num-connections,picture-url)?format=json
and puting it to official linkedin API console https://apigee.com/console/linkedin gives same error. Meanwhile decodin URL to https://api.linkedin.com/v1/people/~:(id,formatted-name,picture-url,location,industry,headline,public-profile-url) is working perfectly in console.
Best,
Nick
I was testing and trying to find out the reason of demo not working and discovered that ProfileCurrentMember failes with 404 error and message from LinkedIn:
"Could not find person based on: ~%3A%28id%2Cformatted-name%2Cpicture-url%2Clocation%2Cindustry%2Cheadline%2Cpublic-profile-url%29"
https://api.linkedin.com/v1/people/~%3A%28id%2Cformatted-name%2Cpicture-url%2Clocation%2Cindustry%2Cheadline%2Cpublic-profile-url%29 |
| |
I think that it may be related to URL encoding as when I try to call basic info API https://api.linkedin.com/v1/people/~?format=json it works fine but as soon as I add profile fields I start having this error. Ifhttps://api.linkedin.com/v1/people/~:(id,num-connections,picture-url)?format=json
and puting it to official linkedin API console https://apigee.com/console/linkedin gives same error. Meanwhile decodin URL to https://api.linkedin.com/v1/people/~:(id,formatted-name,picture-url,location,industry,headline,public-profile-url) is working perfectly in console.
Nick