Amadeus Flight Offers API - amadeus

{
"errors": [
{
"status": 503,
"title": "No available service for processing the request.",
"code": 19,
"source": {
"pointer": "shopping/flight-offers"
}
}
]
}
I get the above error when I call the Flight Offers API (https://test.api.amadeus.com/v1/shopping/flight-offers?origin=NBO&destination=MBA&departureDate=2018-12-10&adults=1&travelClass=ECONOMY&nonStop=true&currency=KES&max=50)on the Amadeus API Explorer. What could be the issue?

We had a technical issue with the API, it's fixed now.
Sorry for the incovinience

Related

Google Fit API Rest create data source

I'm learning how to use Google Fit API and right now I'm trying to do the examples Google offers to explore the OAuth 2.0 Playground.
There's one example to create a data source whose code is:
POST
https://www.googleapis.com/fitness/v1/users/me/dataSources
{
"name": "example-fit-heart-rate",
"dataStreamId":
"raw:com.google.heart_rate.bpm:1234567890:Example Fit:example-fit-hrm-1:123456",
"dataType": {
"field": [{
"name": "bpm",
"format": "floatPoint"
}],
"name": "com.google.heart_rate.bpm"
},
"application": {
"packageName": "com.example.fit.someapp",
"version": "1.0"
},
"device": {
"model": "example-fit-hrm-1",
"version": "1",
"type": "watch",
"uid": "123456",
"manufacturer":"Example Fit"
},
"type": "raw"
}
when I write that code down in the OAuth Playground I have this error message:
{
"error": {
"status": "INVALID_ARGUMENT",
"message": "Expected dataStreamId to be [raw:com.google.heart_rate.bpm:com.example.fit.someapp:Example Fit:example-fit-hrm-1:123456], but was [raw:com.google.heart_rate.bpm:1234567890:Example Fit:example-fit-hrm-1:123456]",
"code": 400,
"errors": [
{
"reason": "invalidArgument",
"message": "Expected dataStreamId to be [raw:com.google.heart_rate.bpm:com.example.fit.someapp:Example Fit:example-fit-hrm-1:123456], but was [raw:com.google.heart_rate.bpm:1234567890:Example Fit:example-fit-hrm-1:123456]",
"domain": "global"
}
]
}
}
I guess is because of the structure of the dataStreamID but I find it strange because I didn't change any code from the Google site. Also I tried to delete the dataStreamID, change the numbers, try this format type:dataType.name:developer project number:device.manufacturer:device.model:device.uid:dataStreamName
but I have no results.
I'm no pretty sure of how does the dataStreamID structure works so if anyone could explain it to me that would be great.
The link of this Google Fit site:
[https://developers.google.com/fit/rest/v1/workout?hl=es-419]
Hope someone can help me.
Thank you!!!

The request includes at least one invalid\/malformed connection photo id

I'm using Google StreetView Publish API to connect photos in a virtual tour and to some external photos on Google StreetView such as a road.
This is the API I use:
https://developers.google.com/streetview/publish/reference/rest/v1/photo/update
And this is the body of the request:
{
"pose": {
"heading": 26,
"latLngPair": {
"latitude": 47.707604844777,
"longitude": -124.41849471719
}
},
"places": [
{
"place_id": "ChIJvcvraDvfjVQR45a-VRk0lGs"
}
],
"connections": [
{
"target": {
"id": "CAoSLEFGMVFpcE5fWGtUZTFWV3dxRm9tOEFlRHVmYVdvTmdDR2NueVZ0dzhid0ZX"
}
},
{
"target": {
"id": "rQfq6hLfyFVfC0V43rrWDw"
}
}
],
"captureTime": {
"seconds": "1653027016"
}
}
But I'm getting this error message when I'm trying to add external panorama ID ({"target":{"id": "rQfq6hLfyFVfC0V43rrWDw"}} to the connections array.
{
"error": {
"code": 400,
"message": "The request includes at least one invalid\/malformed connection photo id.",
"status": "INVALID_ARGUMENT",
"details": [
{
"#type": "type.googleapis.com\/google.rpc.ErrorInfo",
"metadata": {
"EXTERNAL_MESSAGE": "The request includes at least one invalid\/malformed connection photo id."
}
}
]
}
}
Does Google let to connect your panoramas to the Google StreetViews panoramas such as street photos, etc? Or what I was doing wrong? Thank you in advance
You can not link your panoramas directly to Google Street View panoramas.
For a while, Google connected the tours automatically, if they were in a certain range. They stopped doing this and undid those connections, so at the moment both exist side by side on the same map.

INVALID_ARGUMENT error with Google Analytics Reporting API

I'm trying to do a request to the userActivity.search method,
this is the payload that I'm trying to do:
{
"viewId": "<VIEW ID>",
"dateRange": {
"startDate": "7daysAgo",
"endDate": "today"
},
"user": {
"type": "CLIENT_ID",
"userId": "<USER ID>"
}
}
But I'm stuck getting this error:
{
"error": {
"code": 400,
"message": "CLIENT_ID: <ID> not found.",
"status": "INVALID_ARGUMENT"
}
}
The ClientId I get previously at other GA endpoint that list the ClientIds that I need to get more details.
What am I doing wrong?

call ebay api of bulk_migrate_listing then Error 2003

I tried to call https://api.ebay.com/sell/inventory/v1/bulk_migrate_listing, then response code is 2003
My request is :
{
"requests": [
{
"listingId": "160009220563"
}
]
}
Response body like this :
{
"errors": [
{
"errorId": 2003,
"domain": "ACCESS",
"category": "APPLICATION",
"message": "Internal error",
"longMessage": "There was a problem with an eBay internal system or process. Contact eBay developer support for assistance",
"parameters": [
{
"name": "reason",
"value": "Failed to transform underlying error response, see logs."
}
]
}
]
}

Not Found error when charging Square API

The Square REST API docs state that I should get a list of my locations and then use a returned location code when I call the transactions endpoint (to charge a credit card). I am doing exactly this but the returned error says that the merchant has no location with the supplied ID.
I have tried this with and without the location_id in the JSON sent to the transactions endpoint, since it is a path variable. Same result. I have also seen on Square's API FAQ that the usual cause of a 404 not found is the card nonce being created wrong, but this response clearly says the location ID is not valid.
I have tested this with Postman and JSON and I can see that the location code is correct. Here are my calls and the responses:
This is a GET request:
https://connect.squareup.com/v2/locations
And here is the response:
{
"locations": [
{
"id": "FPVPFZ4DXXXXX",
"name": "MyCompany",
"address": {
"address_line_1": "123 Candy Lane",
"address_line_2": "",
"locality": "Smithfield",
"administrative_district_level_1": "RI",
"postal_code": "02917",
"country": "US"
},
"timezone": "America/Los_Angeles",
"capabilities": [
"CREDIT_CARD_PROCESSING"
]
},
{
"id": "4FHNAN1WXXXXX",
"name": "MyCompany2",
"address": {
"address_line_1": "567 Smith Street",
"address_line_2": "",
"locality": "Greenville",
"administrative_district_level_1": "RI",
"postal_code": "02828-2910",
"country": "US"
},
"timezone": "America/Los_Angeles",
"capabilities": [
"CREDIT_CARD_PROCESSING"
]
}
]
}
I modified the returned IDs a bit in the above example.
Next I make a call to charge a card to this uri:
https://connect.squareup.com/v2/locations/FPVPFZ4DXXXXX/transactions
With this body:
{
"note":"",
"idempotency_key":"azsxdcfvrtrewsdf",
"location_id":"FPVPFZ4DXXXXX",
"shipping_address":{
"address_line_1":"123 My Street",
"address_line_2":null,
"locality":"Greenville",
"administrative_district_level_1":"RI",
"postal_code":"02828",
"country":"US"
},
"billing_address":{
"address_line_1":"123 My Street",
"address_line_2":null,
"locality":"Greenville",
"administrative_district_level_1":"RI",
"postal_code":"02828",
"country":"US"
},
"card_nonce":"CBASEPPW7fjdUHe-3jP6ZZ4kvE0gAQ",
"reference_id":"RT-12345678",
"amount_money":{
"amount":12500,
"currency":"USD"
},
"delay_capture":true,
"buyer_email_address":"jim#xxxxxxxxxx.net",
"customer_id":"JIM"
}
And I get this response:
{
"errors": [
{
"category": "INVALID_REQUEST_ERROR",
"code": "NOT_FOUND",
"detail": "This merchant does not have a location with the ID `FPVPFZ4DXXXXX`.",
"field": "location_id"
}
]
}
So the location ID matches exactly the ID returned by the locations endpoint.
Can someone familiar with this API help me out? Square's docs and support is sadly lacking.
I think the issue here is that you have tried to use your sandbox credentials (sandbox-sq0idp-defoUOlu...) to charge against your production location FPVPFZXXXXX. If you call ListLocations with your sandbox credentials, you should get a different location that you can then do sandbox charges with.