I use flight delay prediction api for China domestic flight prediction. The API give an Error 500: Internal Server Error.
Here are my api request url given by the api documentation web page and response info.
Thanks!
Liao Chen
https://test.api.amadeus.com/v1/travel/predictions/flight-delay?originLocationCode=PKX&destinationLocationCode=KWE&departureDate=2021-08-11&departureTime=2021-08-11T15%3A15%3A00&arrivalDate=2021-08-11&arrivalTime=2021-08-11T18%3A15%3A00&aircraftCode=737&carrierCode=CZ&flightNumber=6188&duration=PT3H
{
"errors": [
{
"code": 141,
"detail": "ModelError: Received server error (500) from model with message \"<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 3.2 Final//EN\">\n<title>500 Internal Server Error</title>\n<h1>Internal Server Error</h1>\n<p>The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.</p>\n\". See https://eu-west-1.console.aws.amazon.com/cloudwatch/home?region=eu-west-1#logEventViewer:group=/aws/sagemaker/Endpoints/layla-all-v2 in account 740907634312 for more information.\n{\n RespMetadata: {\n StatusCode: 424,\n RequestID: \"1cc2ca6d-59eb-494d-9a2c-f21c568c3346\"\n },\n LogStreamArn: \"arn:aws:logs:eu-west-1:740907634312:log-group:/aws/sagemaker/Endpoints/layla-all-v2\",\n Message_: \"Received server error (500) from model with message \\\"<!DOCTYPE HTML PUBLIC \\\"-//W3C//DTD HTML 3.2 Final//EN\\\">\\n<title>500 Internal Server Error</title>\\n<h1>Internal Server Error</h1>\\n<p>The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.</p>\\n\\\". See https://eu-west-1.console.aws.amazon.com/cloudwatch/home?region=eu-west-1#logEventViewer:group=/aws/sagemaker/Endpoints/layla-all-v2 in account 740907634312 for more information.\",\n OriginalMessage: \"<!DOCTYPE HTML PUBLIC \\\"-//W3C//DTD HTML 3.2 Final//EN\\\">\\n<title>500 Internal Server Error</title>\\n<h1>Internal Server Error</h1>\\n<p>The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.</p>\\n\",\n OriginalStatusCode: 500\n}",
"status": 500,
"title": "UNEXPECTED ERROR"
}
]
}
The departure and arrival times in your request have the wrong format. According to the documentation they have to be in HH:mm:ss format.
Related
I'm new to the WorldPay integration development.
I'm having difficulty when I am sending an authorization request from one of our applications and I got this response from the api .
Client error: POST https://try.access.worldpay.com/payments/authorizations resulted in a 400 Bad Request response: {"errorName":"bodyDoesNotMatchSchema","message":"The json body provided does not match the expected schema","validationE (truncated...)
My problem is I was unable to see the complete error message because the response has been truncated. Is there a way to prevent that issue?
Using the Postman collection for Amadeus for Developers I can successfully get access token and execute any api endpoint in the test environment (test.api.amadeus.com)
But after signing up successfully for Production Environment (without Flight Create Offer), I am able to get access token from Production (api.amadeus.com) BUT all api endpoint execution results in 401 error (Code: 701 - Wrong authentication credentials)
Below is the error in postman
{
"errors": [
{
"status": 401,
"code": 701,
"title": "Wrong authentication credentials.",
"source": {
"pointer": "uri"
}
}
]
}
i have made sure the bearer token is valid and my api calls are pointed to api.amadeus.com using the Prodction Key and Secret.
I have been in contact with Amadeus email helpline (self-service.apis#amadeus.com) for the last 3 weeks, and after each week they instructed me to reset my account password and wait 2 hours before making the call, which i did three times now and ended up with the same error.
I hope someone higher in the tech department will notice my question and will be able to shed some light as to why your system is not letting me call production environment.
will be eagerly waiting for some advise.....
Happened to me as well, try to generate an access token few more times and use it, for me is suddenly worked
I am trying to send FAX using POSTMAN using following URL "https://platform.devtest.ringcentral.com/restapi/v1.0/account/~/extension/****88004/fax"
and I'm getting:
{
"errorCode": "CMN-408",
"message": "In order to call this API endpoint, user needs to have [OutboundFaxes] permission for requested resource.",
"errors": [
{
"errorCode": "CMN-408",
"message": "In order to call this API endpoint, user needs to have [OutboundFaxes] permission for requested resource.",
"permissionName": "OutboundFaxes"
}
],
"permissionName": "OutboundFaxes"
}
There was a problem in Bearer Token at the time of making Send Fax request.
Because I was using primary account details for generating Token and at the time of sending FAX I was using extensionid of extension 102 and Bearer Token was generated with Main account extension 101. That is why it was throwing [OutboundFaxes] permission error.
To send FAX with ExtensionId of extension 102 , then generate the token using subaccount 102 details instead of main account.
I have successfully reproduced the issue.
test case
The root cause is just what #Jack said: authorize with extension 101 then try to send the fax with extension 102.
The error message is
{ errorCode: 'CMN-408',
message: 'In order to call this API endpoint, user needs to have [OutboundFaxes] permission for requested resource.',
errors:
[ { errorCode: 'CMN-408',
message: 'In order to call this API endpoint, user needs to have [OutboundFaxes] permission for requested resource.',
permissionName: 'OutboundFaxes' } ],
permissionName: 'OutboundFaxes' }
I think the error message needs to be improved. It's very hard to figure out the root cause by reading it. I have reported this issue to RingCentral engineering team.
FCM HTTP v1 API supposed to return error code "UNREGISTERED" when device is unregistered (app uninstalled). However API returns 404 "Requested entity was not found".
Have anyone experienced this? Is this the expected one? There is no mention about this anywhere in the documentation.
Is it safe to assume device is unregistered when 404 error with the message "Requested entity was not found" received?
Following is the full body of the error received.
{
"error": {
"code": 404,
"message": "Requested entity was not found.",
"errors": [
{
"message": "Requested entity was not found.",
"domain": "global",
"reason": "notFound"
}
],
"status": "NOT_FOUND"
}
}
Exception:
Caused by: com.google.firebase.messaging.FirebaseMessagingException: Requested entity was not found.
at com.google.firebase.messaging.FirebaseMessaging.handleSendHttpError(FirebaseMessaging.java:266) ~[firebase-admin-5.9.0.jar:?]
For reference API documentation:
https://firebase.google.com/docs/reference/fcm/rest/v1/projects.messages
https://firebase.google.com/docs/reference/fcm/rest/v1/ErrorCode
Yes, I've experienced this with the firebase-admin-node module, which has been updated recently to map NOT_FOUND to an "unregistered" error, so it appears that it is an expected response.
https://github.com/firebase/firebase-admin-node/commit/069c9cd50502b0fa7cc6843ea3ef9d8d85dca9b9#diff-ce3edf3ab3ed8957259b6bd4035a0256R617
(Though it looks to be the status being NOT_FOUND is the key info rather than the "Requested entity was not found" message)
One thing you may want to confirm is unregistered tokens from different browsers/devices. I.e., I think unregistered tokens from chrome returned a different error than one from firefox.
We face error 404 error code when sending notifications to Unregistered Devices via the old FCM endpoint:
https://fcm.googleapis.com/fcm/send
The documentation for API v1 has been updated and and does not contain this error code.
This is an internal server error so it seems to be an issue on Pinterest's side. I've tried a few things but these accounts always seem to have the internal error.
Here's an example URL that caused the problem:
URL: https://api.pinterest.com/v1/boards/533324849561780294/pins?access_token=AX1gRVqQ2O-VNVVlWy1wAkz3JDvAFDeLJQ7Eom1C53m7hgAuWgAAAAA&fields=url,creator,created_at,counts,image,color,media,attribution,note,link
Exception Error: HTTP request failed! HTTP/1.1 500 INTERNAL SERVER ERROR
Response:
{"message": "A InstantContentBlockField was passed an unknown block_type: text", "type": "api"}
Remove "link" from the fields you will get normal response.