Issues seen so far: **Content-Language is not defaulting to `en-US` (which is different than the ENUMS list of `en_US`) and must be added to the request headers when the error pops up **Marketplace ID doc references ENUMS at (
http://developer.ebay.com/devzone/rest/api-ref/inventory/extra/ffr__pst.Rqst.mrktplcId.html) which should point to (
http://developer.ebay.com/devzone/rest/ebay-rest/content/rest-request-components.html). _MAJOR ISSUE_ because the first uses a "_" while the correct docs use a "-" separator. **Inventory Item Errors** - `aspects` formatting issue - Content-Language Error - Cannot delete Inventory Items > always returns 204 but nothing is ever deleted... **Item Group Errors** - Need to remove `aspects` due to example formatting - `aspectsImageVariesBy` will error with more than two > must remove one of the Array strings and a `specification` to get past this error - Content-Language Error - Cannot find `variantSKUs` that are _in_ the Sandbox system and returned on GET Inventory Items **Product Compatability** - Content-Language Error - Cannot find `variantSKUs` that are _in_ the Sandbox system and returned on GET Inventory Items **Offer** - Content-Language Error - Cannot find valid Inventory Item based on `sku` - I am sure thee is more, but cannot get past the "sku" error to fully test this section I am hesitant to start with the Account, Fulfillment, and Marketing APIs given the errors seen in Inventory. - Is this only a Sandbox thing? - Do production APIs work as document? - Should differences be expected between the environments? Please advise on a path forward...
Hi briapowel_31, Are you able to reply back via the email account
firstname.lastname@example.org that you provided? Or you can login to https://developer.ebay.com/my/support/tickets and update the support ticket we created for you. Best Regards,
@briapowel_31, We are sorry hear that the inventory API's were not working as per the documentation. We are working on fixing the API documentation related to the Marketplace ID, aspects formatting issue in the sample, aspectsImageVariesBy in the inventory item group. The aspectsImageVariesBy is defined as an array so that it can be expanded in future, currently it can vary only by a single aspect. We tried the various scenarios, such as delete inventory item, create inventory item group and publish offer, We were able successfully perform the operations. If you could share the "RlogId" that is sent as part of the response headers, it could help us in triaging the issue and getting back to you.
Hi briapowel_31, We are searching server logs for the problematic API requests. I'll send you a private comment to get your sandbox seller UserID for which the delete failed to understand the issue in the meantime, Regards,
Hi briapowel_31, Would you please send your eBay Developer Account's contact email address or the account's username via an private comment? Here are the steps for posting a private comment: 1. click on 'Click to add comment" button under the latest Answer 2. before click 'Submit' button, please select 'Viewable by moderator', Best Regards,
#### Inventory DELETE Delete DELETE
https://api.sandbox.ebay.com/sell/inventory/v1/inventory_item/item-1481294662597 _ Answer: This call has no response payload ( HTTP status code 204 No Content). The statement "There is no output payload with this response. A successful call contains an HTTP status code of 200" in [Deleting an Inventory Item sample] is wrong. We will get it fixed soon. _ **Response: Ok.** This never results in item being deleted from the inventory. Our growing list of inventory can be seen here GET _Answer: This is a bug and we plan to get it fixed in Q1 2017_ **Response: Ok. Is this something that also affects Production? Meaning: Can we code against an anticipated result and ignore the issue in Sandbox?** #### Inventory Group Create PUT _Answer: This is expected, The SKU provided in the Inventory_group call might have not been created by the time inventory_Group call is invoked. It is mandatory to create inventory_item records for all the SKU provided in the inventory_item_group_ **Response: The SKUs being used in the call are Inventory.Items created very much prior to the call since they are IDs that would not be deleted in the First and Second issues.** #### Create Offer POST _We will need your sandbox user information to debug the issue._ **Response: I will follow up with these via email.**