Retrieve Profile from LinkedIn API by URL - api

As the API suggests I should be able to access my (or any other person's) profile information using public profile URL. However, using the Rest console I haven't been able to get the correct result.
I've tried both of these:
http://api.linkedin.com/v1/people/url=http%3a%2f%2fwww.linkedin.com%2fpub%2falireza-noori%2f51%2fa99%2fba9
http://api.linkedin.com/v1/people/url=http%3a%2f%2fwww.linkedin.com%2fpub%2falireza-noori%2f51%2fa99%2fba9:public
None of them worked. The result is this:
<?xml version="1.0" encoding="UTF-8"?>
<error>
<status>401</status>
<timestamp>1348521763449</timestamp>
<request-id>6MGM1IK1U7</request-id>
<error-code>0</error-code>
<message>[unauthorized]. OAU:w_vW1JF73R-J97_wH3_Iut3i7kL9netWMe90_OMcAkI9mVWggQzip-ssCmwKWyJU|*01|*01|*01:1348521763:ZN/JXOqHRNm4wKsDX+vzlbSC3yY=</message>
</error>

This looks like an issue with the REST Console:
https://developer.linkedin.com/comment/16197#comment-16197

Related

Failed to get blob content present in my Azure storage container using Postman

I am trying to get blob content present in my Azure storage container using Postman.
I created a Service Principal in Azure Ad and got access token successfully using scope as https://storage.azure.com/.default
I am trying to call query in Postman like below:
GET
https://storageaccountname.blob.core.windows.net/containername/filename
When I am calling the above query to get the blob, I got the below error:
<?xml version="1.0" encoding="utf-8"?>
<Error>
<Code>AuthenticationFailed</Code>
<Message>Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.
RequestId:d60dec8d-401e-0084-0ccd-8be567000000
Time:2022-06-27T15:33:38.4195186Z</Message>
<AuthenticationErrorDetail>Authentication scheme Bearer is not supported in this version.</AuthenticationErrorDetail>
</Error>
What does the above error mean? Please help me to get rid of the error.
The error usually occurs if you missed adding x-ms-version header while calling the query.
I tried to reproduce the same in my environment and got the same error like below:
To resolve the error, I added x-ms-version header like below and got the blob content successfully:

SharePoint REST API GetFileByServerRelativeUrl not working

I'm trying to fetch a file, which is downloable in the following URL https://notarealurl.com/sites/name/subname/My%20Folder/test.htm with the following method:
fetch("/_api/web/GetFileByServerRelativeUrl('/sites/name/subname/My%20Folder/test.htm')/$value");
However it returns 404. I've tried with and without decoding the URL. Also, using the following request, doesn't return any file, just an almost empty response. Request:
fetch("/_api/web/GetFolderByServerRelativeUrl('/sites/name/subname/My%20Folder')/files");
Response:
<?xml version="1.0" encoding="utf-8"?><feed xml:base="https://notarealurl.com/_api/" xmlns="http://www.w3.org/2005/Atom" xmlns:d="http://schemas.microsoft.com/ado/2007/08/dataservices" xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata" xmlns:georss="http://www.georss.org/georss" xmlns:gml="http://www.opengis.net/gml"><id>ab8997b7-04a9-4e43-a63f-486e9477e31b</id><title /><updated>2020-04-08T12:00:40Z</updated><author><name /></author></feed>
The correct API URL begins from the parent directory, the correct one is:
fetch("/sites/name/subname/_api/web/GetFileByServerRelativeUrl('/sites/name/subname/My%20Folder/test.htm')/$value");
I tested the following endpoint and it works well.
_spPageContextInfo.webAbsoluteUrl/_api/web/GetFileByServerRelativeUrl('_spPageContextInfo.webServerRelativeUrl/DocuentLibraryName/DocumentName')/$value
And here is one similar threads for your reference:
How to download file from document Library using Rest Api
Best Regards,
Baker Kong

Getting Login Faliure with error code 0

I'm using Yodlee SOAP API endpoints and in my error logs I'm getting Site Refresh Status as LOGIN_FAILURE with error code 0 (which as I understand is not an error according to Yodlee docs). I was wondering what could be the cause of this? Is it an expected behavior? I'm assuming this is not a successful login.
Here is the returned xml:
<?xml version='1.0' encoding='utf-8'?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<ns21:getSiteRefreshInfoResponse xmlns:ns21="http://refresh.refresh.core.soap.yodlee.com">
<getSiteRefreshInfoReturn><siteRefreshStatus>LOGIN_FAILURE</siteRefreshStatus>
<siteRefreshMode>NORMAL_REFRESH_MODE</siteRefreshMode>
<code>0</code>
</getSiteRefreshInfoReturn>
</ns21:getSiteRefreshInfoResponse>
</soapenv:Body></soapenv:Envelope>
Thanks,
I contacted Yodlee Support and I got the answer that it is expected behaviour and users need to login again to get the instant refresh and refreshing sites should work again.

Unable to save resource prestashop webservice

I am new to prestashop web service ,when I add new customer it says one error .
RETURN HTTP BODY
<?xml version="1.0" encoding="UTF-8"?>
<prestashop xmlns:xlink="http://www.w3.org/1999/xlink">
<errors>
<error>
<code><![CDATA[46]]></code>
<message><![CDATA[Unable to save resource]]></message>
</error>
</errors>
</prestashop>
can you guys help me how to solve this error..
Error similar to this are documented before. Activate DEBUG MODE and you will be able to see detailed error.
Good luck.

Yodlee Token authentication failed for cobrand/user Stale conversation credentials</errorDetail>

I sometime get this error while trying to add Accounts(v1.0/jsonsdk/SiteAccountManagement/addSiteAccount1) or get MFA Response(v1.0/jsonsdk/Refresh/getMFAResponseForSite)
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Errors xmlns="http://namespace.yodlee.com/pfm/2009/Error">
<Error>
<errorDetail>Token authentication failed for cobrand/user Stale conversation credentials</errorDetail>
</Error>
</Errors>
can someone help me that issue.
Thank you.
Yodlee doesn't allow multiple user login and hence this exception comes when you have logged in the user again by calling the Login(/authenticate/login​) API and still using the old userSessionToken.
Please use the login (/authenticate/login​) call once and use the same userSessionToken for all the API calls for next 25-30 minutes.