The same thing seems to have happened two years ago public-profile-url causing error, but the approved solution on that question is not solving this problem.
Any connections requests requesting the field 'public-profile-url' throws the following error:
https://api.linkedin.com/v1/people/~/connections:(public-profile-url)?start=0&oauth2_access_token=<token>
<error>
<status>500</status>
<timestamp>1491329264595</timestamp>
<request-id>8IJSBKJHQR</request-id>
<error-code>0</error-code>
<message>Internal API server error</message>
</error>
If this is just an issue with their API, I'd love to get LinkedIn's attention on the matter.
Edit: Interestingly, I found a specific Linkedin connection that is causing the failure (by adjusting the 'start' and 'count' args). It's probably not wise to post that here, but I can provide that information to LinkedIn staff, if need be.
Edit 2: I found replacing 'public-profile' with 'site-standard-profile-request' does function as a workaround. It's not exactly the same thing, but close enough if your user is already using oauth
Same problem, in my case solved removing the "site-standard-profile-request" and the "current-share" attributes from the linkedin v1 people request.
Here is the working api url:
https://api.linkedin.com/v1/people/~:(id,first-name,last-name,maiden-name,formatted-name,phonetic-first-name,phonetic-last-name,formatted-phonetic-name,headline,location,industry,num-connections,num-connections-capped,summary,specialties,positions,picture-url,picture-urls::(original),site-standard-profile-request,api-standard-profile-request)
Related
I'm currently developing a little algorithm to solve the VRP. I herefore use the HERE Matrix Routing API to identify the actual travel times. I just came across the issue, that the retrieved status url after submitting the matrix seems to not accept the API key authorization. Here a little exapmle:
After submitting my matrix, I try to access the status of my calculation via the status url as described in the documentation:
https://matrix.router.hereapi.com/v8/matrix/{matrixId}/status?apiKey={apiKey}
as well as with the returned status url after submitting the request (which is basically the above URL prefilled and with resolved forwarding):
https://aws-eu-west-1.matrix.router.hereapi.com/v8/matrix/{matrixId}/status?apiKey={apiKey}
From my understanding and the way how it's documented, I expect this to be working. Instead, I'm receiving an error code 401, Unauthorized: No credentials found
My request succeeds, when I'm deleting the /status after the matrixId. Is this the expected behaviour or did I reveal a little bug?
Thanks for your help!
BR, Difreg
This is unfortunately due to a combination of how the service operates, and how some client libraries are configured to automatically follow HTTP redirects, like Python requests.
I answered a similar question a few days ago, and you can see the answer here.
Hopefully that helps you figure it out, but if it doesn't, feel free to ask again here.
Preface: I submitted a support ticket to LinkedIn about this but they redirected me here with the response:
I am sorry for the inconvenience this has caused to you. I request you to kindly use the below link to contact Stack overflow for your API related query: https://www.linkedin.com/help/linkedin/answer/53170?hcppcid=homepage
What I sent in my ticket:
Starting over the weekend (8/1), we began seeing an increase in 409 Conflict responses. According to LinkedIn's documentation this indicates that the post is a duplicate of another post created in the last 10 minutes, however looking into this ourselves we've verified that this is not the case. We've made no changes to our integration, so we know this is nothing on our end either.
Here's an example response:
{"message":"com.linkedin.content.common.ResponseException: RestliServiceException thrown in chimera; Write conflict when trying to update UGC: urn:li:share:[redacted]","status":409}
A similar issue posted on StackOverflow at the time of writing this: https://stackoverflow.com/questions/63232641/com-linkedin-restli-client-restliresponseexception-errors-since-august-01st-with
^ This has since been removed for being a tech support question, which I agree with, but LinkedIn's not giving us any other options here.
I'm not sure why they redirected me to Stack Overflow or how they expect Stack Overflow to help here, so I've replied to their ticket but made this post in the meantime just in case.
Any ideas for what might be wrong on our end would be appreciated!
I am integrating Woo-commerce API’s in my wordpress site using Woo-commerce official rest sdk. I made a link using authentication endpoint URL. When I click the link it takes the user to Woo-commerce authentication page, where user login and Approve the request.
After approving the request it should take me to return url which i mention in the link. Instead it shows me the following error.
Error: An error occurred in the request and at the time were unable to send the consumer data.
I was having the same issue as well, and in my case, the return_url on my backend server was accepting GET requests, I changed it to POST, and everything worked perfectly. I hope it helps!
I know it's late for the answer but writing it for the people who will face the same issue in the future.
I was having the same issue and my problem was that the callback_url was wrong which was creating the error internally. So if you are getting this error, most probably your callback_url is not correct, please check that properly.
For whoever Shattique's answer
did not work,
check the response status code sent by the callback_url handler.
Anything other than 200 will throw the error in OP's question.
Here is link to woocommerce github repo,
where it throws the error.
TLDR: Make sure callback_url handler returns statusCode: 200
https://maps.googleapis.com/maps/api/geocode/xml?address=Bahnhofstra%C3%9Fe+12,+37603+Holzminden,+Germany(&)key=myAPIKey
The above URL which returned Google geo-codes 2 days before, today it returned Zero_reuslts status. I tried for different address it was the same case. So I fixed them by adding (&) between key and Address.
I tried same method with premium account, it returns error as "Unable to authenticate the request. Provided 'signature' is not valid for the provided client ID, or the provided 'client' is not valid.."
But if I use the old method URL encoding as draffted below, it gives Zero_results as status.
https://maps.googleapis.com/maps/api/geocode/xml?address=Bahnhofstra%C3%9Fe+12,+37603+Holzminden,+Germanyclient=gme-myClientIDsignature=myCryptKey
I am facing the problem from today, could someone help me to resolve this issue.
Change your call and use the Places API instead of the Geocoding API:
https://maps.googleapis.com/maps/api/place/textsearch/json?key=YOUR_API_KEY&query=Bahnhofstraße+12,+37603+Holzminden,+Germany
I was able to solve the problem this way because I was facing the same problem with ZERO RESULTS errors since yesterday. Seems like Google has changed something in the Geocoding API.
There are 2 issues mixed up here.
ZERO_RESULTS are due to the new forward geocoder in the Geocoder API no longer returning poor result for incomplete or ambiguous requests. The same would happen for badly formatted requests, e.g.:
http://maps.google.com/maps/api/geocode/json?address=Bahnhofstra%C3%9Fe+12,+37603+Holzminden,+Germanykey=YOUR_API_KEY
returns ZERO_RESULTS because it's missing the & character between Germany and key. That's easy to fix:
http://maps.google.com/maps/api/geocode/json?address=Bahnhofstra%C3%9Fe+12,+37603+Holzminden,+Germany&key=YOUR_API_KEY
Once that's fixed, your client id and signature are actually being checked, and if you get the Unable to authenticate the request error it means your request is malformed. See Digital signatures for details on how to correctly sign your requests, and here's a tool that does it well, so you can check your signatures against those generated by it:
https://m4b-url-signer.appspot.com
When sending customers to Paypal from my website I am seeing a new error message I've never spotted before:
Error Detected
We are sorry, we are experiencing temporary difficulties. Please try again later. If this error occurred while making a payment, avoid duplicate payments by checking your Account Overview before resending a payment.
Message 3005
Googling this message suggests it is just one shown to the general public when Paypal is overloaded....but I don't think that can apply to me becuase the Paypal site responds normally to other parts of my website which use a HTML link. It is when I use an ASP.NET Response.Redirect that I see the error.
I have checked the URL is correct and encoded correctly. So I really would like clarification that message 3005 is indeed one that can be shown when the incoming request is erroneous, as well as when the Paypal site is under heavy load.
Is this generic message shown in both circumstances? Is Response.Redirect acceptable?
"Googling this message suggests it is just one shown to the general public when Paypal is overloaded..."
And that's why you can't always trust Google results.
No, a '3005 error' does not mean PayPal is 'overloaded'. It is a generic error which can be returned for various internal and external reasons.
It's the PayPal equivalent of 'Something went wrong', without actually saying what went wrong.
Can you reproduce this error consistently? And if so, what are the steps to reproduce it?
Can you include your code?