I check trends regarding to REST API of twitter. get trends
Generally it works well. But sometimes I get 404 error.
After some minutes it comes back.
Error code is:
{"errors":[{"message":"Sorry, that page does not exist","code":34}]}
Does anyone had this issue? What would you recommend ?
Please check this link, it gives 404 now.
https://api.twitter.com/1/trends/1.json
how often are you accessing this call - are you sure you are not breaching the rate limit? If not breaching, this could possibly be an issue on the twitter end and you would need to handle the error message, use the previously cached response for your application till you get an updated feed from twitter. hope this helps
Related
We’re seeing intermittent 403s from the media.licdn.com 4 server - some users can see the avatar, but others get a 403 at the exact same URL.
I know this is fundamentally a LinkedIn issue, but since the Auth0 plugin is borrowing these images, any insight on why this might be happening or if perhaps there is a more stable image URL that should be used instead?
Example:
https://media.licdn.com/mpr/mprx/0_xfyAKR4RCit_89KnV18tTuHYCgxEknxzV68c35dR1lPozspzp18BrGHRtg0FQsxv0S8tTfWY3IO7cb8U4kDYbhdjnIOfcbDnMkDYq34UiI-7cb-gZlhvQzXc8rGiQAyj2xAO-VZNny76NijVo3Hf1E
I am using the below url for getting the share count for twitter
https://cdn.syndication.twitter.com/widgets/tweetbutton/count.json?url=google.com
It is working finee before yesterday then sudden its get broken and I am getting below response from twitter when calling above url
"errors":
{
"message": "Sorry, that page does not exist",
"code": 34
}
Then I have also tried below url for getting share count
https://cdn.api.twitter.com/1/urls/count.json?url=www.google.com
http://urls.api.twitter.com/1/urls/count.json?url=www.google.com
It also result in same error
Please anyone can help me how can I get the proper share count in twitter, And I am not so good in English I apologies for that
Twitter disabled this feature a few days ago that's the reason why it is not working anymore.
You can find more information by reading this blog post.
Twitter shut down this API, but you can get an alternative at http://opensharecount.com
I have a CMS account an I'm trying to get earnings data from content owners report on Analytics API using OAuth 2.0 . Whenever I'm trying to do this through my website, I get the following error ;
Error calling GET https://www.googleapis.com/youtube/analytics/v1/reports?ids=contentOwner%3D%3DContentOwnerID&start-date=2005-01-01&end-date=2015-11-26&metrics=views%2Cearnings%2Clikes%2Cdislikes%2Cshares%2Ccomments&dimensions=30DayTotals&filters=channel%3D%3DChannel_ID: (403) Forbidden
I'm doing the same thing on TRY IT page and it works fine.
I'm thinking that I'm having issues with authenticating my domain. What do you think is the problem? How can I solve this issue?
Thank you,
403 means nobody has access to a page. As you noticed, you may have access to a similar page, but not to this one. It is not a matter of authentication. Authentication problems give a status 401 (meaning it can be fixed by adding proper authentication); 403 cannot be fixed.
Finally, I solved the problem..
Whoever will have this issue, please use the CMS user's OAuth 2.0 credentials instead of using channel credentials..
I use Oauth via Microsoft and it has worked fine for a while, then a couple of weeks ago (can't remember exactly when) i got some tweet or something from someone saying that they had problems signing in with MS Oauth.
The error i get is this.
https://login.live.com/err.srf?lc=1033#error=invalid_request&error_description=The+provided+value+for+the+input+parameter+'redirect_uri'+is+not+valid.+The+expected+value+is+'https://login.live.com/oauth20_desktop.srf'+or+a+URL+which+matches+the+redirect+URI+registered+for+this+client+application.
The page actually says
"We're unable to complete your request
Microsoft account is experiencing technical problems. Please try again later."
And that indicates that they may actually have some issues but i think it's been like this for a while so i suspect it's just some generic error.
If i look at my request it says.
client_id=[MY CLIENT ID]&scope=wl.basic&response_type=code&redirect_uri=http://dev.ohso.se/login/ExternalLoginCallback/?provider=microsoft&sid=[some id]
I do get the same error on both my dev app and the production app i have setup.
This is how my callback URLs look like. I have tried to add URLS both with ExternalLoginCallback and externallogincallback but it doesn't seems to work. It looks like it's saved but it's gone when you return to the page.
Anyone know how to contat MS to at least report this bug and maybe also get hold of someone that can help debug my problem?
/Ola
OK, got it. The issue is with your request URL, remove / character from ..back/?provid.... Your request URL should be
client_id=[MY CLIENT ID]&scope=wl.basic&response_type=code&redirect_uri=http://dev.ohso.se/login/ExternalLoginCallback?provider=microsoft&sid=[some id]
and you can have any redirect URL #MS
http://dev.ohso.se/login/ExternalLoginCallback
or
http://dev.ohso.se/login/ExternalLoginCallback/
I recently got oAuth working for my iOS app to log in to Tumblr. Now I'm having trouble posting using the new API calls. I'm able to generate a request and prepare Autorization headers but I'm still getting errors.
Here is my URL:
http://api.tumblr.com/v2/blog/my_blog.tumblr.com/post?tweet=no&tags=my%2C%20app&state=published&type=text&title=Hello&body=I%2520finally%2520got%2520this%2520to%2520work
Here is my Authorization header with x's in place of sensitive info:
Authorization = "OAuth realm=\"\", oauth_consumer_key=\"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\", oauth_token=\"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\", oauth_signature_method=\"HMAC-SHA1\", oauth_signature=\"XXXXXXXXXXXXXXXXXXXXXXXXX\", oauth_timestamp=\"1347656207\", oauth_nonce=\"XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX\", oauth_version=\"1.0\"";
There error I receive:
{"meta":{"status":400,"msg":"Bad Request"},"response":{"errors":["Post cannot be empty."]}}
Does anyone have experience with this? I've been working at it for at least 20 hours over a two day period.
Any help is greatly appreciated.
EDIT: I've also tried including authorization data in the url (i.e., oauth_token, oauth_consumer_key), essentially the stuff found in the header. When I do this I get a 401 "Not Authorized" error, which I know isn't correct because I just successfully called "http://api.tumblr.com/v2/user/info" which requires a valid authorization.
found solution, see explanation here.