After running smoothly for an entire year, a 'create' call to the Google Documents List API started giving 403 Forbidden errors.
Other methods work fine with the same access_token parameter. This started around December 7th very consistently across all of our users invoking this call.
This API just recently got a deprecation policy where it will stay intact until April 2015. To be fair, I don't expect the Google Drive team to be actively supporting this API, but wondering if there is a chance that something on the Google Drive transition could be related to this inconsistency.
Is anyone else experiencing unexpected errors on the Google Documents List API? Any clues as to what is going on, and how deep might the issue be?
Thank you!
Related
We got the request from google to submit YouTube API Audit form and we have submitted with all information but it seems our Console project with YouTube Data API still not activated properly because of status display "Active" but the daily quota is blank.
When I am going to update daily quota with any number but it seems set with blank on page refresh and we are not able to make any single request successful.
We are working with this console project and YouTube API for the last 5 years without any issue but in the last few months we are getting so many issues like first, we have verified OAuth screen with requested scopes and it has taken 20-25 days in the verification process and published. Now, facing another issue about limit quota and audit form.
Right now we are getting below error as attached in screenshot while going to authenticate my google account with the permission of Manage YouTube data API.
There is no contact support provided and I have submitted form 3 times but no back reply from support so waiting since 1 month to get work as normal.
Let me know if anyone has idea!
Error:
Error calling GET https://www.googleapis.com/youtube/v3/channels?part=contentDetails&mine=true:
(403) Access Not Configured. YouTube Data API has not been used in project xxxxxxx before or it is disabled. Enable it by visiting
https://console.developers.google.com/apis/api/youtube.googleapis.com/overview?project=xxxxxxx then retry.
If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.
Access Not Configured. Quota limit issue
This means that you do not have any quota to use the API. You need to apply for an additional quota within the Google developer console. It took me about three months to get a quota on my project.
This is not the same as going through the verification process all though it is similar. Unfortunately, you must have missed an email you were probably notified a while ago that Google was locking down the quotas and you should apply before losing the quota on your existing project.
There is no support other than going though the form and simply waiting until google choices to grant you some quota or they tell you they wont. This is the price of developing with a free api google gets chose how they want to allow us to access things.
For years we have used the YouTube search API to provide a simple YouTube fallback for smart-tvs with no native YouTube app available. The Queries Per Day for our registered app has been set to "unlimited" trough all this time AFAIK, and we only use the youtube.search-list API.
Suddenly, three weeks back, access to the search function was no longer working. Turns out the quota for daily queries was set to blank(no number, no nothing). When trying to change it we get "enter a number in the range 0 to ."
First of all we linked the app to a billing account to be able to adjust the quota. But it was still not working. Then we contacted YouTube and filled out a big form to increase the quota. We got reply from YouTube that the quota request was granted. But we are still not able to set/change the quota. I've tried replying to to quota mail, but I guess the mail is not monitored.
We see others have had similar issues, and the solution seems to have been to contact YouTube. But we have not found any way to contact them regarding YouTube data API support queries except here on stackoverflow(we do not have a paid support plan). So we're posting here hoping that anyone from YouTube can respond - or to get tips from users that have been in the same situation.
UPDATE:
We have now tried two things:
* Removing and adding back in YouTube data API v3 in the registered app. Did not help
* Activating YouTube data API v3 on another app we have registered - this gave us a daily quota of 10000(but we would definatly prefer not to have to change to another API key)
UPDATE 2:
Info we left out that might be relevant. We recently went trough a process with Google filling out the "YouTube API Services Form"(a google docs form). We went back and forth with the google team, replacing logos, adding ToS links, changing UI etc. until we got a:
"Thanks for your response to the Audit Form. We will conduct our audit based on the information you provided. We will notify you if additional information is needed or when we completed our review. Thank you for your cooperation."
After this we have heard nothing.
Today we can see that the quota is back to 10000... We did send a second request for quota raise and I also sent a mail to the Audit Form team. Not sure which one did the trick - have received no response. And that's probably the most annoying thing about this - the complete lack of feedback.
I experienced the same issue before in one of my projects and I can tell that your access to Youtube data api has been disabled.
TLDR;
I noticed this first because I got the error below when calling Youtube data API.
{ "error": { "errors": [ { "domain": "usageLimits", "reason": "accessNotConfigured", "message": "Access Not Configured. YouTube Data API has not been used in project <my_project_id> before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/youtube.googleapis.com/overview?project=<my_project_id> then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.", "extendedHelp": "https://console.developers.google.com/apis/api/youtube.googleapis.com/overview?project=<my_project_id>" } ]
So I went to the console and checked if the API is enabled (And it was). Then I checked the quota, which I suspect is the issue because I got a blank value in the queries per day. I could still edit the value, but those values didn't take effect. It eventually transitioned to 0 and after that, I can no longer edit it (This is after some editing and refresh).
When I looked at my email, it shows that they sent me an email with the following subject and content.
Subject: [FYI] YouTube disabled your inactive project’s access to YouTube Data API Service
Dear YouTube API Developer,
According to our records, your project has been inactive for the past 90 consecutive days. In accordance with the YouTube API Services Developer Policies (link), we disabled your project’s access to and use of the YouTube Data API Service.
This will not affect other Google API Services that you may have enabled on this project.
For reference, your inactive project number is my_project_number
If you desire to access and use YouTube Data API Service, or believe you were disabled in error, you may complete and submit this form to get in touch with us.
Thanks,
YouTube API Services team
The form was included in the email, but since you haven't received one, here's what you need to do as stated here.
If the API is indeed enabled, then this means that your project’s access to YouTube Data API Service has been disabled.
You should’ve received a notice via email regarding this action, which also contains the steps that need to be taken to regain the project’s access. But just in case you missed it, please fill out and submit the exceptions form below:
https://support.google.com/youtube/contact/yt_api_form?hl=en
The alternative, outright solution is to create a new project where you will get the default 10,000 quota.
As of this week I am suddenly getting gateway timeout from Graph when my mail search finds no results.
I am using a query like this one:
https://graph.microsoft.com/v1.0/users/shared#notreal.com/mailFolders/AllItems/messages?$search="participants:some.person#fake.com"&$select=from,subject,HasAttachments,Id,SentDateTime&$top=100
This is a Graph query which requests up to 100 emails from the Office 365 mailbox of shared#notreal.com where the sender or receiver includes some.person#fake.com. shared#notreal.com is a mailbox that is shared with the account making the call.
My app is authenticated with the oauth2 authentication code flow and has been granted all necessary permissions.
This has been working for about a year. But starting a few days ago, this query only succeeds if results are found. When no results are found, the query takes 30 seconds, Graph returns UnknownError and the response is 504 with reasonphrase Gateway Timeout.
It seems as though something has changed in the Graph API - or perhaps in the Office 365 API, but I can't find any mention of it anywhere.
Microsoft specifically directs questions about the Graph API to stackoverflow, so here I am. I hope the right people are reading.
Why has this suddenly started happening and how can I fix it?
Update: there are now numerous reports of this issue, confirming that it's at Microsoft's end.
Github issue
We saw this question and were actively investigating this kast week. With July 4th long weekend I hadn't got back to this thread until now.
This issue has been resolved on the back end of the service and you should not be seeing this issue anymore.
Thank you so much for sharing the service issue here.
This issue seems to be resolved on our end now.
Resumable uploads are giving me 403 errors with the PUT requests after creating the upload session.
I've used app level tokens for resumable uploads recently and they worked fine. I previously tried them months ago and they were not working and I remember something about them not being supported.
I don't find that text that states that in the documentation. Are they supported or is there another issue?
Thanks
We tracked down the issue to a new feature that was recently enabled and shut it off. The app-only scenarios should now be working as expected so please let us know if you continue to see issues.
as of about 3 hours ago every call to the Doclist API using 2-legged OAuth started failing with "500 Internal Error" messages.
We have verified this from multiple systems (App Engine and local apps) using different libraries, and across domains in Asia, US and Europe.
The problem does NOT occur if normal user authentication is used - only 2LO is affected.
Unfortunately this issue affects thousands of students using our tools.
http://code.google.com/a/google.com/p/apps-api-issues/issues/detail?id=3233&thanks=3233&ts=1347419864
Jan
This is tracked at http://code.google.com/a/google.com/p/apps-api-issues/issues/detail?id=3233 and the fix should be live very soon.
UPDATE: everything is now back to normal