In the API Explorer I have a different response than through the API. Why?!
Hello,
API Explorer response for https://api.ebay.com/sell/inventory/v1/bulk_migrate_listing
{
"responses": [
{
"statusCode": 400,
"listingId": "184762324743",
"marketplaceId": "EBAY_DE",
"errors": [
{
"errorId": 25002,
"domain": "API_INVENTORY",
"subdomain": "Selling",
"category": "REQUEST",
"message": "A user error has occurred. The listing SKU cannot be null or empty."
}
]
}
]
}Response for API the same URL and the same parameters as in API explorer
{
"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."
}]
}]
}
Same account. Production in both cases. Same parameters. Yes, I know that you need to set the SKU for the offer before migration, but that's not the problem.
API Explorer gives more specific error details, API doesn't. So what? if I have a general error in the API, I have to make a query through API Explorer to get to know the details?!
Tell me what I'm doing wrong. I want the same error descriptions in the API.
Regards
das-company
Posted 3 years ago·Last reply 3 years ago
2 comments
five_notch_trading_post
·3 years agofor a request payload of:
I receive in both the explorer and directly the following response.
If I don't send a payload, I receive in both the following:
If I add a header of Accept:text/html to the headers section of the API Explorer I receive the exact error message you get.
So my guess is it is likely a header issue, to a lesser extent perhaps something with the payload, -- in whatever client you are using to interface with the API.
das-company
OP3 years agoHello,
thank you very much for your help.
I checked the request headers as you suggested.
The bulkMigrateListing method requires a header in the request: 'Accept', 'application/json' to return detailed errors. This method works fine without this header, it just doesn't return detailed error information if the header is missing.
Now I have this response for an attempt to migrate a multi-variant offer that has no SKU/groupId set.
Thank you for your time
Regards