I am using the eBay API to develop part of an application I am writting...maybe you are not aware that to use it the developer pays everytime their program access the API. That can become very expensive very fast....and that equates to more fees for us users.

And do not assume the API is all bells and roses either...it has constant technical issues...

I do understand your frustration as I am a seller in Pottery & Glass and we are pretty much foo-bar'd right now...I have come up witha work around but given the volume you probably list in it would not be practical.

but, I create a new auction lot in AW2k. Then I preview the lot view the "source" which opens notepad where I make a few fast mods of the HTML so the img tags point to my website (using find & replace makes this fast...) Next I copy all of the HTML between the body-tags which I then paste into Turbo Lister which will support item specifics and finsh the listing...basically I only use TL as a lister itself...back in AW2k I set the auction lot to "queued for listing" then I repeat this for all the auctions I need to list...when I am done I simply tell aw2k to update my website which allows will put all of your auction pics on the site wiht the same name as used in the preview...then I set TL to upload of all of the newly created listings. After the auctions are listed you can use the aw2k IMPORT function to grab the current auctions...

Use a special listing profile so you can keep the dummy auction lots seperate and can delete them when ya want...

It is a kludge but it is SOMETHING that works...and while not ideal it works for for the interim while Thom can get the next version done...

And almost every listing program was caught flat footed here...evne those who use the API as ebay had nothing set in stone until very late in the game...they are ALL playing catchup...and on top of that eBay has admitted this is simply the tip of the iceberg in terms of changes coming...it is gonna be a looooong summer...