I have very limited knowledge when working with APIs and am hoping someone will be able to shine a light on an issue I am facing. Corrections will be very much appreciated if anything I mentioned below is incorrect.
I primarily work with Etsy modules. I manage several stores on Etsy and my understanding is that by running scenarios through Make’s modules, it utilizes their Etsy developer key for authorization so I am not required to create my own developer accounts for each store. I was also advised by a rep that by doing this through Make, it will keep the stores safe and unlinked from each other.
Etsy has two versions of their API; V2 and V3. I believe the current Etsy modules are based on their V2 API but I am not sure if it is limited to it. The V2 API is due to sunset by the end of this year so I am looking to migrate over to V3 as soon as possible.
When I tried running the Etsy API call module, I used this URL for V3, method GET: /v3/application/buyer-taxonomy/nodes
Our Etsy modules are based on Etsy API version 2, as you have correctly pointed out.
The development team is already aware of this issue and V3 has already begun implementation and is in the testing phase at the moment. I can’t give you an ETA right now but I hope it doesn’t take too long.
Nothing yet, I emailed yesterday to chase up progress and stress the urgency. As I said before, it might be worth emailing them to escalate it. The more people that do this I’m sire it’ll go up the queue!
Hello everyone @here thanks a lot for raising this issue in the community!
I just wanted to let you know that our dev team is working on launching the new version of the app that’s compliant with the latest Etsy API. However, we still have a few things to sort out before we can roll it out, so there’s no specific ETA at this moment.
I’ll keep an eye on things and let you know as soon as I hear anything new.