API v3 product batching, images & adjusted_grandtotal

[Marius Bojorovas]

Hello,
We're done with out Etsy integration for the most part, but wanted to double check if there we're some better ways of using the new API v3

Our first problem is:
We need to sync the user's inventory -> that means we need to get the user's products with variations and images.

1. So we are using https://developer.etsy.com/documentation/reference/#operation/getListingsByShop endpoint, to get 100 listings. But the problem is, we can't include images or inventory (variations) here.

2. Then using  https://developer.etsy.com/documentation/reference/#operation/getListingsByListingIds endpoint, to get images for those 100 listings. But why did you remove the ability to include them in "getListingsByShop" or in "getListingsInventory"?

3. During the last step we use https://developer.etsy.com/documentation/reference/#operation/getListingInventory endpoint, to get specific listing's inventory (variations).

The problem is, we can get only 1 listing at the time (if i'm not being mistaken), in API v2 we had the ability to batch up to 100 products, but now we can't. It gets really strict with your API limits, and our users get slow imports because we need to use reduced call rates to not go over said limits.

It would be great if API v3 would have the ability to include inventory (variations) in the "getListingsByShop" call or at least allow us to batch products. If there are any other easier ways to solve our problem please let us now.

Our second problem is:
We need to sync user's orders -> that means we need to get user's orders, and keep their information up to date:

step 1 -> we sync orders through this endpoint https://developer.etsy.com/documentation/reference/#operation/getShopReceipts
step 2 -> order gets cancelled on etsy
step 3 -> we sync again -> but the order no longer comes back through https://developer.etsy.com/documentation/reference/#operation/getShopReceipts

Currently we solve this problem by, every time before syncing orders -> checking every new (not shipped) order on our end, and one by one calling endpoint https://developer.etsy.com/documentation/reference/#operation/getShopReceipt to see is order state is canceled. Why can't the canceled order info come back with "getShopReceipts", it is a very important piece order of information.
If there are any other easier ways to solve our problem please let us know how.

Our third problem is:

Besides knowing when an order has been canceled, we also need to know when the order has been refunded. In the past we used to do this by checking the "adjusted_grandtotal". If it differed from the basic order total that meant the order had been refunded in some capacity. The "adjusted_grandtotal" data is now gone. Is there some other way that we can track this change?

Thank You

[James Wu]

Great questions, good quality and clear.

I have the same "first problem", I'm doing exactly what you suggested, and I'm also taking care of the rate limits.

for the "second problem", I think you can sync by "min_last_modified" instead of "min_created".

Hope it helps

James

[James Wu]

Great questions, good quality and clear.

I have the same "first problem" and doing exactly same as you suggested. (need to take care of rate limit)

For "second problem", you can try sync using min_last_modified instead of min_created.

Hope it helps

James

On Tuesday, March 29, 2022 at 2:47:34 PM UTC+2 mar...@multiorders.com wrote:

[Marius Bojorovas]

Checking by "min_last_modified" would reduce some calls, but we'd really hope to be able to just see if the order is canceled or not, but as far as we've seen everywhere else that is not possible, nor is it possible to see refunded orders.