Wrong (and confusing) error message when trying to delete an image that's already deleted. #865
Unanswered
MickaelBNeron
asked this question in
Q&A
Replies: 1 comment
-
Or even a 204... Anything distinct to the case where the resource is already deleted would be better. Right now, my program has to look at the error message to understand the image was already deleted and ignore the error... If getting a 400, there's no other way of knowing if it's due to the resource already being deleting or an issue with the format of the request. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I was trying to delete an image via https://openapi.etsy.com/v3/application/shops/40737763/listings/1395058264/images/4589268962, but was getting a 400 (BadRequest) with the following content: {"error":"The listing_id 1395058264 does not belong to the same shop that is associated with the listing_image_id 4589268962."}.
It turns out, the image was already deleted, but this error message suggested a different problem and it took me a while to figure out the actual problem.
I think a 404 would be more appropriate, or at least a clearer error message.
Beta Was this translation helpful? Give feedback.
All reactions