Fwd: Creating a new listing gives error saying I need a listing_id

[david olick]

Getting an odd error message when creating a new listing...

X-Etsy-Request-Uuid:

7vlU48ne2qf7Ef1duzptyaXGTbL3

Error message:

object has validation errors on the following field(s): listing_id (listing_id can't be empty) : listing_id (listing_id can't be empty);

Raw data:

POST https://openapi.etsy.com/v2/private/listings?oauth_consumer_key=[deleted]&oauth_nonce=[deleted]&oauth_signature=[deleted]&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1491246427&oauth_token=&oauth_version=1.0

Content-Length: 1380
Content-Type: multipart/form-data; boundary=xYzZY

--xYzZY

Content-Disposition: form-data; name="language"



en

--xYzZY

Content-Disposition: form-data; name="state"



active

--xYzZY

Content-Disposition: form-data; name="quantity"



1

--xYzZY

Content-Disposition: form-data; name="title"



Green necklace, green choker, shell necklace, green shell necklace, green copper necklace, statement necklace

--xYzZY

Content-Disposition: form-data; name="description"



Copper and green shell choker made with copper wire and green shell beads. 12.5 inches / 32cm with ribbon tie.

--xYzZY

Content-Disposition: form-data; name="price"



25.00

--xYzZY

Content-Disposition: form-data; name="materials"



silver,shell

--xYzZY

Content-Disposition: form-data; name="category_id"



69151567

--xYzZY

Content-Disposition: form-data; name="tags"



green necklace,green choker,shell necklace,green shell necklace,green copper necklac,statement necklace,Birthday present,shell jewellery,green jewellery,copper jewellery,copper choker,shell choker

--xYzZY

Content-Disposition: form-data; name="shipping_template_id"



1176572816

--xYzZY

Content-Disposition: form-data; name="shop_section_id"



14329531

--xYzZY

Content-Disposition: form-data; name="who_made"



i_did

--xYzZY

Content-Disposition: form-data; name="is_supply"



false

--xYzZY

Content-Disposition: form-data; name="when_made"



2010_2017

--xYzZY--

[Michael Herlihy]

Reporting same error. 

[lylesback2]

I'm getting the same errors on our end.

Invalid auth/bad request (got a 400, expected HTTP/1.1 20X or a redirect) : object has validation errors on the following field(s): listing_id (listing_id can't be empty) : listing_id (listing_id can't be empty);

We made no changes to our code in a couple of weeks. All of a sudden it stopped working today.

[Al EaForesman]

Hi David

 

I am seeing the same issue and would like to add my voice and data to yours.

 

Here is my raw http data (note I have striped the OAuth info)

CALL:

POST /v2/listings HTTP/1.1

Host: openapi.etsy.com

Content-Type: application/x-www-form-urlencoded

Content-Length: 198

Authorization: OAuth oauth_consumer_key="XXXXXXXXXX",oauth_nonce="XXXXXXXXXX",oauth_signature="XXXXXXXXXXXXXX",oauth_signature_method="HMAC-SHA1",oauth_timestamp="1491322138",oauth_token="XXXXXXXXXXXX",oauth_version="1.0"

Connection: close

category_id=68888136&description=this+is+a+thing&is_supply=0&language=en&price=5&quantity=1&recipient=not_specified&shipping_template_id=21376712901&title=fred&when_made=made_to_order&who_made=i_did

REPLY:

HTTP/1.1 400 Bad Request

Server: Apache

X-Etsy-Request-Uuid: v596CRkMbISX0riLJWELnVFfVKew

X-RateLimit-Limit: 10000

X-RateLimit-Remaining: 9971

X-Error-Detail: object has validation errors on the following field(s): listing_id (listing_id can't be empty) : listing_id (listing_id can't be empty);

Cache-Control: private

Content-Length: 137

Content-Type: text/plain;charset=UTF-8

Date: Tue, 04 Apr 2017 16:08:59 GMT

Connection: close

Set-Cookie: uaid=uaid%3D05ToOEKYquVC9lr5JeJkDaaZN-qh%26_now%3D1491322139%26_slt%3DxdH1q9LA%26_kid%3D1%26_ver%3D1%26_mac%3DtWIS-Z51rdozy4w6ATwzJH9fBtqsJ8TGY2bWsQUJqvw.; expires=Sat, 05-May-2018 08:27:19 GMT; Max-Age=34186700; path=/; domain=.etsy.com; secure; HttpOnly

Set-Cookie: user_prefs=ZBDrugA4TQ_Egkq-jZvVvVj3SBdjZACCiMdHpWF0dF5pTo4OyUQsAwA.; expires=Wed, 04-Apr-2018 16:08:59 GMT; Max-Age=31536000; path=/; domain=.etsy.com

object has validation errors on the following field(s): listing_id (listing_id can't be empty) : listing_id (listing_id can't be empty); 

On Tuesday, April 4, 2017 at 7:32:27 AM UTC-7, david olick wrote:

[Iñaki Abete]

Same here.

[Iñaki Abete]

FYI, I found that including also a "taxonomy_id" it works:

{

    "quantity": 1,

    "title": "10KT White Gold 1.75ctw Amethyst & Diamond Cocktail Ring, 11.44gm. Size: 5.25",

    "description": "This brightly polished 10KT white gold ring contains one amethyst in the center, surrounded by single cut diamonds, all prong set in a raised basket style setting. A twisted rope design finishes the look, all set atop a five layer shank.",

    "price": 720,

    "shipping_template_id": 474167845,

    "state": "draft",

    "category_id": 69150467,

    "taxonomy_id": 1,

    "who_made": "someone_else",

    "is_supply": true,

    "when_made": "1980s"

}

[Michael Herlihy]

Thanks Inaki for discovering the source of the problem you are a life saver!

If you are posting a category_id (old system) there is a typo in the debug:

listing_id can't be empty

The correct debug message should be:

Sorry we dropped support for old seller categories... please use taxonomy_id instead.

Or simply

taxonomy_id can't be empty.

That would of saved us three days of frustration.

[lylesback2]

Adding taxonomy_id => 1 solved our issue. Thanks guys for pointing that workaround out.

On Tuesday, April 4, 2017 at 10:32:27 AM UTC-4, david olick wrote:

[Michael Herlihy]

So I was mistaken they do support category_id as long as you have a taxonomy_id=1

[Developer Etsy]

Hi all,

A couple of things:

1. This was a bug, not an intentional change. We'd pushed a fix to validate incoming category IDs, and in doing so included some code that expected a listing ID to be present at a point where it wasn't. That bug (and the validation issue!) should now be fixed.

2. We do want folks to stop using category IDs and move to using taxonomy IDs, but when we do that we'll be communicating with you rather than springing it on you. See https://www.etsy.com/developers/documentation/reference/listing#section_taxonomy for the move to taxonomy ID (and note that the Listing endpoint does return "suggested_taxonomy_id" if you want help moving your listings to the new taxonomy, or want to build that into a tool for your users to use).

3. Taxonomy ID over-rides category ID, so if you send taxonomy_id=1 you are putting that listing into the Accessories category (taxonomy ID 1), not the category you were expecting. Please don't do that unless you're actually listing accessories (and even then, you should be as explicit as possible and use one of the child taxonomy nodes of Accessories).

Apologies for the confusion and problems this caused. I hope the above points make sense and clarify things.

Ian

Justin Sheckler

Developer API Lead

Etsy.com

[Michael Herlihy]

Thanks Justin for clarifying this ... appreciate your time.

[david olick]

It's complaining about taxonomy_id's again.  Can you please fix this issue?

"This listing does not have a taxonomy_id set."

--
You received this message because you are subscribed to the Google Groups "Etsy API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to etsy-api-v2+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Developer Etsy]

Is this with createListing still? Normally I'd expect that error if you were using an inventory endpoint and were using properties from the new taxonomy.

Ian

[david olick]

It looks like it happens when we're updating a listing.

What are we supposed to do when the taxonomy_id and almost all other fields are null?

{"count":1,"results":[{"listing_id":221399453,"state":"active","user_id":52404418,"category_id":69150437,"title":"Flash Sale 90's Silky Floral Cami Dress","description":"90's super silky floral mini lingerie dress.\nExact Measurments:\nLength: 36"\nWidth:15"\nBust: 34"\nWaist: 30"\nHips: 38" \n\nSize: Small \nMaterials: Polyester\nTag: Sedu\n\nModels Measurments:\nHeight: 5'7"\nBust: 34"\nWaist: 28"\nHips: 32"","creation_tsz":1487284816,"ending_tsz":1497649216,"original_creation_tsz":1423095389,"last_modified_tsz":1492021077,"price":"18.00","currency_code":"USD","quantity":1,"tags":["vintage lingerie","silky mini dress","silky lingerie","floral mini dress","valentines dress","valentines lingerie","valentines day"],"category_path":["Vintage"],"category_path_ids":[69150437],"materials":["polyester"],"shop_section_id":15937160,"featured_rank":null,"state_tsz":

1491043678,"url":"https:\/\/www.etsy.com\/listing\/221399453\/flash-sale-90s-silky-floral-cami-dress?utm_source=fotofuze&utm_medium=api&utm_campaign=api","views":200,"num_favorers":21,"shipping_template_id":7595906466,"processing_min":1,"processing_max":3,"who_made":"someone_else","is_supply":"false","when_made":"before_1998","item_weight":null,"item_weight_units":null,"item_length":null,"item_width":null,"item_height":null,"item_dimensions_unit":null,"is_private":false,"recipient":null,"occasion":null,"style":null,"non_taxable":false,"is_customizable":false,"is_digital":false,"file_data":"","should_auto_renew":true,"language":"en-US","has_variations":false,"taxonomy_id":null,"taxonomy_path":null,"used_manufacturer":false,"ShippingInfo":[{"shipping_info_id":12294257033,"origin_country_id":209,"destination_country_id":79,"currency_code":"USD","primary_cost":"15.00","secondary_cost":"1.99","listing_id":221399453,"region_id":null,"origin_country_name":"United States","destinati

on_country_name":"Canada"},{"shipping_info_id":11715105554,"origin_country_id":209,"destination_country_id":167,"currency_code":"USD","primary_cost":"22.00","secondary_cost":"4.25","listing_id":221399453,"region_id":null,"origin_country_name":"United States","destination_country_name":"New Zealand"},{"shipping_info_id":11711252473,"origin_country_id":209,"destination_country_id":209,"currency_code":"USD","primary_cost":"4.99","secondary_cost":"0.99","listing_id":221399453,"region_id":null,"origin_country_name":"United States","destination_country_name":"United States"},{"shipping_info_id":11710692236,"origin_country_id":209,"destination_country_id":null,"currency_code":"USD","primary_cost":"22.75","secondary_cost":"1.99","listing_id":221399453,"region_id":null,"origin_country_name":"United States","destination_country_name":"Everywhere Else"}]}],"params":{"listing_id":"221399453","quantity":null,"title":"Flash Sale 90's Silky Floral Cami Dress","description":null,"price"

:null,"wholesale_price":null,"materials":null,"renew":null,"shipping_template_id":null,"shop_section_id":null,"state":"active","image_ids":null,"is_customizable":null,"item_weight":null,"item_length":null,"item_width":null,"item_height":null,"item_weight_unit":null,"item_dimensions_unit":null,"non_taxable":null,"category_id":null,"taxonomy_id":null,"tags":null,"should_auto_renew":null,"who_made":null,"is_supply":null,"when_made":null,"recipient":null,"occasion":null,"style":null,"shipping_profile_id":null,"processing_min":null,"processing_max":null,"featured_rank":null},"type":"Listing","pagination":{}}

On Thu, Apr 13, 2017 at 1:59 PM, 'Developer Etsy' via Etsy API <etsy-...@googlegroups.com> wrote:

Is this with createListing still? Normally I'd expect that error if you were using an inventory endpoint and were using properties from the new taxonomy.

Ian

--

[david olick]

It looks like it's related to category_id's when the taxonomy_id hasn't been set yet.

Here's a list of category_id's I've identified cause the taxonomy_id error:

"category_id":69160487, "category_path":["Jewelry","Necklace","Beaded"], "category_path_ids":[68887482,69151567,69160487], "suggested_taxonomy_id":1218, "taxonomy_path":["Jewelry","Necklaces","Beaded Necklaces"]

"category_id":69176111, "category_path":["Supplies","Bead","Metal"], "category_path_ids":[69150433,69151309,69176111], "suggested_taxonomy_id":6238, "taxonomy_path":["Craft Supplies & Tools","Beads, Gems & Cabochons","Beads"]

"category_id":69161131, "category_path":["Jewelry","Bracelet","Stone"], "category_path_ids":[68887482,68888548,69161131], "suggested_taxonomy_id":1193, "taxonomy_path":["Jewelry","Bracelets"]

"category_id":69161391, "category_path":["Jewelry","Earrings","Dangle"], "category_path_ids":[68887482,69151501,69161391], "suggested_taxonomy_id":1208,"taxonomy_path":["Jewelry","Earrings","Dangle & Drop Earrings"]

"category_id":69159857, "category_path":["Jewelry","Necklace","Stone"], "category_path_ids":[68887482,69151567,69159857], "suggested_taxonomy_id":1217, "taxonomy_path":["Jewelry","Necklaces"]

"category_id":68912476, "category_path":["Supplies","Bead","Plastic"], "category_path_ids":[69150433,69151309,68912476], "suggested_taxonomy_id":6238, "taxonomy_path":["Craft Supplies & Tools","Beads, Gems & Cabochons","Beads"]

"category_id":69160001, "category_path":["Jewelry","Necklace","Charm"], "category_path_ids":[68887482,69151567,69160001], "suggested_taxonomy_id":1222, "taxonomy_path":["Jewelry","Necklaces","Charm Necklaces"]

"category_id":69161579, "category_path":["Jewelry","Earrings","Beaded"], "category_path_ids":[68887482,69151501,69161579], "suggested_taxonomy_id":1203, "taxonomy_path":["Jewelry","Earrings"]

"category_id":68897246, "category_path":["Jewelry","Necklace","Choker"],"category_path_ids":[68887482,69151567,68897246], "suggested_taxonomy_id":1223, "taxonomy_path":["Jewelry","Necklaces","Chokers"]

"category_id":68912680, "category_path":["Supplies","Bead","Semiprecious Stone"], "category_path_ids":[69150433,69151309,68912680], "suggested_taxonomy_id":6238,"taxonomy_path":["Craft Supplies & Tools","Beads, Gems & Cabochons","Beads"]

I'm still doing some digging into my error logs to see if there's any other categories that are causing this issue.