I'm a student creating a demo app using your test API, and am getting the following error when querying the flight destination API (eg. https://test.api.amadeus.com/v1/shopping/flight-destinations?origin=PAR&maxPrice=200)
I don't get any error when querying the same location using the flight offers search API, so it's not an issue with my key/secret, and the location is definitely included in the limited test API dataset.
I'm using the ruby gem (https://github.com/amadeus4dev/amadeus-ruby) but faced the same issue testing the API on postman.
Any help appreciated!
{
"errors": [
{
"status": 500,
"code": 141,
"title": "SYSTEM ERROR HAS OCCURRED",
"detail": "Primitive technical error"
}
]
}
I was having the same issue with the flight-deals endpoint. I submitted a request to Amadeus support and got the following reply:
Unfortunately we are currently having some issues with this API in the test environment. Our technical team is currently looking for a solution, in the meantime if you need to use this endpoint, please move your app to the production environment where the API will work as expected....in this environment you will receive a free amount of transactions each month just like in test
I did try going over to a production environment and I'm not getting technical errors (500's) any more. It does require signing up for payment in case you go beyond the free tier of request volumes. Not clear when they will have the test environment up and running.
Related
I have an application that uses the Microsoft Graph API to read and write emails from a mailbox.
I'm making a request to URL
GET https://graph.microsoft.com/v1.0/users/{user_id}/mailFolders/PublicFoldersRoot/childFolders
This used to work, but since April 2021 it broke and now returns an error
{
"error": {
"code": "ErrorMailboxMoveInProgress",
"message": "Mailbox move in progress. Try again later., Cross Server access is not allowed for mailbox UUID"
}
}
No mailboxes have been initiated to move in my account.
I found the same thread on this issue, but there is no solution yet. Mailbox move in progress.
I didn't find out any workaround. Please help if you know how to fix this.
Apologies for the inconvenience caused to you.
Could you please check if there are any mailboxes being moved?
You can use Poweshell Cmdlet Get-MoveRequest to check if there are any active requests.
If there aren't any, this could be an intermittent issue and should resolve itself without your intervention
However, if this is critical and affecting your production workloads, please reach out to Support as it would be difficult to debug this remotely.
You can also check if there are any service issues affecting your subscription from the Service Health page
Hope this helps. Thanks!
I've created a medium application for API access a while ago, and I've been using it to connect medium accounts to my website and let them publish stories from my website. But it stopped working recently, and I can't access my app anywhere. I should mention that my medium account isn't premium, so I've been thinking that's the problem. The thing is I can't find any info anywhere about medium preventing free users from creating apps. This is where I've managed my apps in the past: Link, but now I get 403. Does anyone have any info about this?
edit: What I forgot to say is, when I try to connect my account, I receive the access/refresh token, but then when I try the "https://api.medium.com/v1/me" endpoint I get
{
"errors": [
{
"message": "Application not found",
"code": 6005
}
]
}
On Friday (6/24/2016) our youtube app crashed giving us the following error.
{
"error": {
"errors": [
{
"domain": "usageLimits",
"reason": "dailyLimitExceededUnreg",
"message": "Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup.",
"extendedHelp": "https://code.google.com/apis/console"
}
],
"code": 403,
"message": "Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup."
}
}
The code that was run was a simple API request to check the state of a video. It has also been running without any problems for over a year.
curl https://www.googleapis.com/youtube/v3/videos?part=contentDetails,status,snippet&key=XXX&id=XXX&maxResults=50
A few thoughts:
This message makes no sense since we are passing our key as a parameter which does authenticate us. I understand this can mean I need to use OAuth but this would be a change since this has been running without errors for over a year.
When I checked our API console I found that the youtube api was marked as disabled (this changed as we enabled it to get a key last year) and I do not see any usage limit errors when I check usage in the console.
I have also found making the request to the API from a browser on my desktop works but using curl on our server gives the usage error. This indicates there is some issue with our server.
Can someone help me understand what's going on? Are there IP blocks for the API? Did Google make a change recently that would have reset my console and caused an error suddenly in our code?
Any thoughts would be greatly appreciated.
"Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup."
I've come across this error before. It's not that complicated. 2 things I can suggest:
You're access token has expired. You need to generate a new one. Read Implementing OAuth 2.0 Authorization.
Register a new API key in you're GDC.
Also, try oAuth Playground for testing.
I'm having this daily limit problem with my ruby code when I try to issue a download request. This is a test program so I am running it in my terminal. I just call the ruby file.
I've followed this guide to quickly get into the Google Drive API.My code is pretty similar to that guide other than my scopes which are:
SCOPE = ["https://www.googleapis.com/auth/drive", "https://www.googleapis.com/auth/drive.file", "https://www.googleapis.com/auth/drive.appfolder", "https://www.googleapis.com/auth/drive.metadata"]
The credentials I am using is oAuth Service Key with "other" selected.
This is the line of code making the call.
content = HTTP.get('https://www.googleapis.com/drive/v3/files/' + file_id + "?alt=media").body
This is the error I am getting from the HTTP call.
{
"error": {
"errors": [
{
"domain": "usageLimits",
"reason": "dailyLimitExceededUnreg",
"message": "Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup.",
"extendedHelp": "https://code.google.com/apis/console"
}
],
"code": 403,
"message": "Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup."
}
}
I've followed this link and created all the necessary credentials to get it working, but still have had no success. Google Drive API is also enabled in my project.
How can you fix this error even after you've set up the Google API project and its credentials?
Edit: Wanted to note that I have search and upload working with the same code. Download is the only one that is giving me errors.
All the suggestions given here are not up to the mark . This is a routine error that Drive API throws and can be easily handled .As soon as you get the error , you can again request the Drive API to consider your request by using a strategy called exponential back-off . This ensures that you make a call to Drive API again , after a specified amount of time . There is a documentation about this issue by Google and is a common issue when you send too many requests at a time .Check this link right here, it is the answer to all your problems that you are facing https://developers.google.com/drive/v3/web/handle-errors#errors_and_suggested_actions . And also request an additional Quota from Google Developers Console . Additional quota can be requested under the Quotas tab in Google Developers Console. You might be lacking enough quota to make the request . The details for same are given in the link i posted above. You should create an account and request Quota as being an unauthenticated user your requests won't last long.Use Google OAuth to authenticate yourself into the Drive API.
I'm using gem omniauth-google-oauth2 to login with google from Rails app.
These days I'm getting this error:
{
"error": {
"errors": [
{
"domain": "usageLimits",
"reason": "accessNotConfigured",
"message": "Access Not Configured. Please use Google Developers Console to activate the API for your project."
}
],
"code": 403,
"message": "Access Not Configured. Please use Google Developers Console to activate the API for your project."
}
}
Same settings would work fine for localhost, but failed frequently and sometime work on production. I have no idea of what's going on? Is Google changing there API recently? What API do I need to enable just to login and get user info?
I came across this problem when updating from omniauth-google-oauth2 0.2.2 to 0.2.4. To resolve the issue, go to your Google Developers Console. Click on "APIs" and enable the "Contacts API" and "Google+ API". This GitHub issue describes the problem in more detail.
We're started experiencing the same issue 20 hours ago, but it's appearing on both production and localhost (which use two separate Google accounts). The strange thing is that we are able to log in every 3 or 4 tries, but not every time.
As far as an API change on Google's end, this issue on omniauth-google-oauth2 seems relevant: https://github.com/zquestz/omniauth-google-oauth2/issues/106. However, this deprecation should not be enforced until September, 2014.
Also, editing the omniauth-google-oauth2 gem directly and changing these lines:
class GoogleOauth2 < OmniAuth::Strategies::OAuth2
BASE_SCOPE_URL = "https://www.googleapis.com/auth/"
DEFAULT_SCOPE = "userinfo.email,userinfo.profile"
to this:
class GoogleOauth2 < OmniAuth::Strategies::OAuth2
BASE_SCOPE_URL = "https://www.googleapis.com/auth/"
DEFAULT_SCOPE = "email,profile"
Yielded this error:
Error: invalid_scope
Some requested scopes were invalid. {invalid=[https://www.googleapis.com/auth/profile, https://www.googleapis.com/auth/email]}
Update:
Quoted from an email from Lever (hire.lever.co):
"The issue stemmed from an bug in a release Google made to the authentication system Lever uses to identify users last night. We were among some apps who lost the ability to verify users via their Google OAuth API. We've been in communication with Google, and we've been told that the release was reverted at 11:30AM PDT."
Google OAuth appears to be fixed for us now.
We found that Billing had been enabled for one of our projects, but no Billing information entered. Disabling Billing for this particular project so far seems to have resolved this issue for us.
The error we were getting was:
{
"error": {
"errors": [
{
"domain": "usageLimits",
"reason": "accessNotConfigured",
"message": "Access Not Configured. Please use Google Developers Console to activate the API for your project."
}
],
"code": 403,
"message": "Access Not Configured. Please use Google Developers Console to activate the API for your project."
}
}
Update: Of course our fix was applied ~ 11:30 AM PDT, so I am I'm voting this was a Google issue.