I'm trying to get hotels catalogue from Amadeus api v3, so far, I found all informations like name, rating, offers ... but still have to get pictures to display the returned data on a front-office.
I tried : view=FULL and view=FULL_ALL_IMAGE doesn't make any changes on the response.
Any help please ? :(
I tried also this request :
'ghttps://api.amadeus.com/v3/hotels/images?hotelId={{Hotels_IDs}}&size=FULL&aspectRatio=16:9'
I get this error message :
`{
"code": 38196,
"title": "Resource not found",
"detail": "The targeted resource doesn't exist",
"status": 404
}`
The Hotel Search v3 doesn't return images. For workarounds check the migration guide.
Related
I am using V5 pinterest API,
https://api.pinterest.com/oauth/?client_id=<CLIENT_ID>&redirect_uri=<REDIRECT_URI>&response_type=code&client_secret=<CLIENT_SECRET>
after this get request I getting below error message
{
"status": "failure",
"code": 11,
"message": "API method not found.",
"endpoint_name": null,
"data": null
}
Any pointers will be helpful to get the successful authentication request to fetch the acess_token
Regards,
Rita
Based on the documentation, the endpoint should be,
https://www.pinterest.com/oauth/
So your request will be like this,
https://www.pinterest.com/oauth/?
client_id={YOUR_CLIENT_ID}&
redirect_uri={YOUR_REDIRECT_URI}&
response_type=code&
scope=boards:read,pins:read
Note that you need at least one scope in the request.
I am using the Qualtrics API to create contacts in a mailing list. In making a call to https://ca1.qualtrics.com/API/v3/mailinglists/ML_identity/contacts I am pushing a json string containing extRef. However, I keep getting the following response:
"httpStatus": "400 - Bad Request",
"error": {
"errorMessage": "Unexpected json key provided: extRef",
"errorCode": "RP_9"
},
The documentation clearly states extRef is what the field is called. What am I missing here?
The field should be externalDataRef instead of extRef (Qualtrics is inconsitent when it comes to that field). See: https://api.qualtrics.com/api-reference/reference/researchCore.json/paths/~1mailinglists~1{mailingListId}~1contacts/post
Note that the API call is specific to Research Core Contacts. XM Directory uses a different API call to add a contact.
When I am tryping to request on ebay inventory API using API Exploler. I am geting the Call Respond Statud code 404.
and Following error message. can anyone help me to solve the issue
{"errors": [
{
"errorId": 25710,
"domain": "API_INVENTORY",
"subdomain": "Selling",
"category": "REQUEST",
"message": "We didn't find the entity you are requesting. Please verify the request"
} ]}
That message means there is an issue either with the item, or the SKU. Maybe you typed the SKU incorrectly. Maybe you're looking in the account of the wrong user.
But my guess... The SKU was of an item that wasn't created with the API, and was instead created manually using eBay's front end. That command only works on items also created by similar commands.
UPDATE : Fix one problem with the content-type of the request which has to be application/vnd.amadeus+json 🤷♂️ After the fix, lot of mails are not able to be parse without additional details. Amadeus support kind of confirmed me that my test mails are from providers that are not supported :/
I try to use Self-Service Trip Parser API https://developers.amadeus.com/self-service/category/trip/api-doc/trip-parser
I did some testing using confirmation emails from well-known brand like Booking or Oui SNCF but with no success and generally got 500 generic errors.
What I do is :
go to gmail, download the message as .eml format
encode it to base 64 base64 -i mail.eml | tr -d '\n' | pbcopy
create the payload to send to Amadeus using own Amadeus Swagger but got 500 errors in most case
{
"data": {
"type": "trip-parser-job",
"content": "<paste mail content>"
}
}
{
"errors": [
{
"code": "38189",
"title": "Internal error",
"detail": "An internal error occurred, please contact your administrator",
"status": "500"
}
]
}
In best case, the job is created, but the status is failure after a few minutes
Only using mail PDF attachment seems to work sometimes.
My questions are simple :
do any of you make it works reliably ?
is there any additional information on support input format or providers ?
is there any worthwhile alternative ?
in all Amadeus Self-Service APIs only some Airport codes work. For example "FRA" works, but "TXL" doesn't. Is this because the API is in Beta and I only use the Sandbox version?
Example:
https://test.api.amadeus.com/v1/shopping/flight-destinations?origin=FRA&oneWay=false&nonStop=false
WORKS
https://test.api.amadeus.com/v1/shopping/flight-destinations?origin=TXL&oneWay=false&nonStop=false
{
"errors": [
{
"status": 500,
"code": 141,
"title": "SYSTEM ERROR HAS OCCURRED",
"detail": "DATA DOMAIN NOT FOUND FOR REQUEST"
}
]
}
The APIs available in the test environment have a limit set of data (cache or fake data).
In the test environment, this API doesn't have data for TXL as origin, for Germany you have FRA and MUC.
So far our data set covers more the US and some big cities in the world. We will publish soon the list of available data on our portal.
You can find the list of available data in the test environment on our GitHub page.