Replies: 1 comment
-
we faced similar issue with different listings in multiple etsy shops, pretty sad but, etsy api support not helpful at all. try to mail to developer@etsy.com, maybe you be lucky :) |
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
-
We have a comercial access app and we are experiencing an issue when requesting data for a user with etsy shop id 25463380.
Here a sample CURL of what we do: (note we do not include in the curl our API_KEY nor the ACCESS_TOKEN of the user).
curl -X GET 'https://api.etsy.com/v3/application/shops/25463380/listings?state=active&offset=45&limit=1&includes=Inventory,Images' -H 'Accept: application/json' -H 'Content-Type: application/x-www-form-urlencoded' -H 'x-api-key: API_KEY' -H 'Authorization: Bearer ACCESS_TOKEN’
In this case, when requesting specifically the element number 45 of the list (or this element is included in the page as per example offset = 30, limit = 30), the endpoint returns BAD GATEWAY: {"error":"Bad Gateway”}. Note the endpoint works fine when requesting listings not containing that specific element (for example, offset 46 - limit 30, or offset 0 limit 44)
Maybe data is malformed? but in this case the API shouldn't be failing as it does.
Beta Was this translation helpful? Give feedback.
All reactions