YouTube V3 API (googleapis.com) returns 404? - youtube-api

I'm using the YouTube V3 API in a Discord application. But for some odd reason, this stopped working about 20 minutes ago. The url http://www.googleapis.com returns a "404 Not Found, That's an error", When only half an hour ago it worked!
Does anyone else have this problem? Can I fix it, or is it just Google?

try using https://www.googleapis.com instead of http://www.googlesapis.com
It looks like you got some typo ins the URL. Also, always use https.

Related

youtube-api on JavaScript backend

After 2 weeks that I was using that API correctly and I have upload a few video on YouTube, today I receive this error when I try to get a new access token:
Error 400: invalid_scope
Some requested scopes were invalid. {invalid=[https://googleapis.com/auth/youtube.upload]}
Also with the old access token that was working yesterday, now I cannot proceed..
Now I can think that YouTube for some reason have blocked me or something like that because I haven't changed the code.. Anyone have experienced something like this? How I can proceed? At least I want to know if I was 'blocked' and for what reason.

YouTube Authentication stopped working

We're using oauth2 authetication for devices in order to allow our app to upload videos to YouTube accounts. This has been working fine for a number of weeks, but when I tried to authorise an account today, when I enter the phase where we poll for a token by calling https://www.googleapis.com/oauth2/v4/token it now returns 428 Precondition required.
I can only find a vague description of this in the global Google API docs. We haven't changed any code so unless Google have changed something at their end, I don't understand why this is suddenly no longer working.
Has anyone else had this issue recently and if you have, do you know of a solution?
Many thanks,
Damien
thanks for the reply. Yes I did debug it and the authentication tokens are correct.
After some experimentation, I've found that what's happening is that the API response for the polling for token call is now returning http status code 428 instead of 400 (for situations where the user hasn't accepted access yet and where the response would be authorization_pending). If I handle this code in the same way as a 428 it all works without problem.
Not sure why Google are now doing this as it can potentially break a lot of apps, but if anyone else is having this issue, you just need to check for code 428 instead.

Sorry, that page does not exist, Error code 34 when getting twitter share count

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

Microsoft oauth login stopped working all of a sudden?

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/

Twitter API 401 - weird

¨
I have a weird reponse from Twitter API. It's Error 401: Unauthorized, but the weird thing is, that it has worked before.
I created a twitter app several days before and generate access token by twitter developers portal. Everything works fine for 18 hours. Then, the service reports 401. Today, I created a new app and update the access settings - consumer key, access token and so on. I did one API call and everything worked fine. But after next request, twitter returned 401.
I have read a lot scenarios when the twitter returns 401 error but I don't know why Twitter returns the error to me.
Thanks for help.
I may sound silly but please check if date and time of the PC or server where the app is installed.
For example if you set your timezone as GMT in your PC then your PC must have exact time of GMT else twitter API will through error. Please check it.
Thanks

Resources