Flight Low-fare Search API not filtering properly by maxPrice - amadeus

I'm trying to use the endpoint Flight Low-fare Search and I realised that it's not filtering properly by maxPrice.
For example, reaching the next endpoint with maxPrice=100.
https://test.api.amadeus.com/v1/shopping/flight-offers?origin=MAD&destination=BIO&departureDate=2018-12-07&returnDate=2018-12-10&adults=1&maxPrice=100&currency=EUR
I'm getting the following result so I think there is an error:
{
"price": {
"total": "185.09",
"totalTaxes": "39.09"
},
"pricePerAdult": {
"total": "185.09",
"totalTaxes": "39.09"
}

This bug has been fixed and deployed in production.

Related

Linkedin endpoint adAnalyticsV2

I am having an issue in getting the data from LinkedIn API , I have got the permissions and trying postman to test endpoint to get data mention below is my get request , every time the response is an empty elements list with 200 ok. any help in this regard will be highly appreciated. I am sure that their is data its not that there is no activity but cant retrieve via api request.
https://api.linkedin.com/v2/adAnalyticsV2?q=analytics&dateRange.start.year=2019&dateRange.start.month=5&dateRange.start.day=28&dateRange.end.year=2021&dateRange.end.month=9&dateRange.end.day=30&timeGranularity=DAILY&pivot=MEMBER_COMPANY&projection=(*,elements*(externalWebsiteConversions,dateRange(*),impressions,landingPageClicks,likes,shares,costInLocalCurrency,pivot,pivotValue~(localizedName)))&fields=externalWebsiteConversions,dateRange,impressions,landingPageClicks,likes,shares,costInLocalCurrency,pivot,pivotValue&accounts[0]=urn:li:sponsoredAccount:123456789
and this is the response every time
{
"paging": {
"count": 10,
"start": 0,
"links": []
},
"elements": []
}

Walmart API Error: WM_CONSUMER.CHANNEL.TYPE set null or invalid

My client has a Walmart marketplace store and we are trying figure out how to successfully make the Walmart API's Multiple Item Inventory for All Ship Nodes API call.
The API production URL is :
https://marketplace.walmartapis.com/v3/inventories
The purpose of this call is getting the inventory of the store using the API.
Unfortunately, we are stuck because we don't know what value to put for WM_CONSUMER.CHANNEL.TYPE.
As a result, the API response is unsuccessful and gives this error:
{
"error": [
{
"code": "INVALID_REQUEST_HEADER.GMP_GATEWAY_API",
"field": "WM_CONSUMER.CHANNEL.TYPE",
"description": "WM_CONSUMER.CHANNEL.TYPE set null or invalid",
"info": "One or more request headers are invalid.",
"severity": "ERROR",
"category": "DATA",
"causes": [],
"errorIdentifiers": {}
}
]
}
Where can the value of WM_CONSUMER.CHANNEL.TYPE be found?
I had the same exact issue. I had to open a ticket with support to get the WM_CONSUMER.CHANNEL.TYPE.
Just an FYI, this didn't solve the problem as the value they gave us still resulted in the API returning the same error code.

Invalid variant ID while creating checkout for Shopify

I am trying to create checkout url using Admin API with following params.
URL: https://shopy-test11.myshopify.com/admin/api/2020-10/checkouts.json
{
"checkout": {
"line_items": [
{
"variant_id": 37033347711169,"quantity": 2
}
]
}
}
Unfortunately its returning below error which is not properly documented anywhere that I could find.
{
"errors": {
"line_items": {
"0": {
"variant_id": [
{
"code": "invalid",
"message": "is invalid",
"options": {}
}
]
}
}
}
}
I also tried Shopify-api ruby gem and got same error. There are some similar issue online, but none answers why that issue is occurring and how to fix it. This is new app under development which will create custom checkout. There's only one sales channel which is "Online Store" and is enabled for all products. Any ideas how to fix this issue? Any help is appreciated.
You seem to be mixing up concepts here. The checkout API is only associated with the Storefront API, and has nothing to do with the Admin API.
So this URL: /admin/api/2020-10/checkouts.json seems to be impossible. There is no endpoint in the admin API for checkouts, whereas, Storefront API which does have checkouts, might be your proper URL. So try that:
/api/2020-10/checkouts.json
And if you have the correct token in your header, it will likely work.

Fleet Api diferent from Route API - Invalid POI

Something isn't correct with HERE API:
This is working if I use https://route.api.here.com
https://route.api.here.com/routing/7.2/calculateroute.json?app_code=**APP_CODE**&app_id=**APP_ID**&waypoint0=geo!40.881402,-8.633051&waypoint1=geo!38.6143899,-1.1041018&mode=fastest;truck;traffic:enabled&language=pt-pt&routeAttributes=shape
This isn't working if I use http://fleet.api.here.com
http://fleet.api.here.com/2/calculateroute.json?app_code=**APP_CODE**&app_id=**APP_ID**&waypoint0=40.881402,-8.633051&waypoint1=38.6143899,-1.1041018&mode=fastest;truck;traffic:enabled&language=pt-pt
I received this error:
{
"issues": [
{
"message": "Cannot match 38.6143899/-1.1041018 onto a road link with 100.0m search radius"
},
{
"message": "Request id: 5c3aee72-e8f5-4c34-b96c-7c3e3cce5c02"
}
],
"response": null,
"error_id": "5c3aee72-e8f5-4c34-b96c-7c3e3cce5c02",
"response_code": "400 Bad Request"
}
But using the link https://tcs.ext.here.com/examples/v3/cost_optimized_route, I saw this:
Meanwhile, I research the API and if i increase the mapMatchRadius option to 500 m is working. It's very strange. The road exists in Here Maps. Someone from the Here Support Team can provide an input?

Firebase Cloud Messaging Reports - not displaying sent count in Reports

We have set "analytics_label" in the message as stated in the documentation and the message is getting delivered as well. But we do not see any entry in the report. Please check our message string and let us know what might be wrong. Appreciate your help.
REST API being called
https://fcm.googleapis.com/fcm/send
Message being sent
{"topic":"81xxxxx42","android":{"priority":"high"},"priority":"high","fcm_options":{"analytics_label":"nwy81xxxxx42"},"data":{"MID":-1,"frm":"99xxxxx32","MTP":9,"msg":""}}
I'm not certain what library you're using or if you're just POSTing directly to the REST API, but looking at code that I know works I think you just need to make fcm_options and analytics_label camel case.
{
"topic": "81xxxxx42",
"android": {
"priority": "high"
},
"priority": "high",
"fcmOptions": {
"analyticsLabel": "nwy81xxxxx42"
},
"data": {
"MID": -1,
"frm": "99xxxxx32",
"MTP": 9,
"msg": ""
}
}