Hi all,
I’m looking for some help troubleshooting an issue I’m running into while trying to update image alt tags for an existing product on Etsy.
Here’s what I’m doing:
- Using the List Shop Listings module to retrieve listing data.
- Passing the results through an Iterator.
- Using OpenAI to generate alt text based on each image.
- Finally, using the Etsy “Make an API Call” module to send a PUT request to update the alt tag.
However, I’m consistently getting a “Resource not found” error. I’ve tried hardcoding both the listing ID and image ID (instead of mapping them) — same result. I’ve also double-checked that both IDs are correct.
I’ve attached screenshots and the setup details. Any guidance or insight into what I might be missing would be greatly appreciated!
Thanks in advance
blueprint (2).json (39.9 KB)
chat-gpt.txt (1.4 KB)
input-make-an-api.txt (461 Bytes)
Iterator.txt (10.1 KB)
List-shop-listing.txt (318.7 KB)
bundle.json (14 Bytes)
Hey Niaz,
which endpoint are you trying to hit with that API call? Can you post a link to it from the Etsy API documentation?
If the URL is correct, then I can see 2 potential issues → you are trying to make a GET request. Updating information should be either POST, PUT or PATCH, depending on what it says in the documentation.
The second potential issue is → you have special symbols in the Result variable, it is possible that this is breaking the JSON file. Try escaping them with a replace() function.
Hi Stoyan,
I was reviewing the Etsy API documentation and the only relevant endpoint I found is for uploading listing images. I was previously using the following endpoint with a PUT request:
/v3/application/listings/{{1.listing_id}}/images/{{22.listing_image_id}}
However, based on their documentation, it appears that I should be using a POST request instead. You can find the reference here:
[Preformatted text](https://developers.etsy.com/documentation/reference/#operation/uploadListingImage)
I also tried hardcoding the alt text (rather than using the GPT-generated result) with POST requet, but encountered the same issue.
Let me know your thoughts.
