etsy
Proposed design portability for /users/{UserId}/profile on V3 - Keep
Current Endpoint Design Currently I can remap some of my implementation against the Etsy V3 API without Using Oauth2. Users of app would not welcome a need to provide access I am happy if we can access public information same as on V2
On V2 profiles can be fetched without special permissions such as /users/{UserId}/profile
This is really needed because in other resources such as Reviews the reviews author information (buyer) is not provided but indeed only the id is so then access to this publicly available information is great.
Search - v3/application/shops?shop_name=ShopName
Reviews - v3/application/shops/{ShopId}/reviews
Proposed Endpoint Design Change Keep the subresource available on V3 . If a user asks for more private information then ask for a Oauth token. For Search and Reviews also avoid adding the need of an Oauth2 token at least for publicly available information.
Why are you proposing this change?
The v3/application/users/{UserId} does request the Oauth token with email_r permissions so I would like to have the /profile subresource available under V3 so the functionality can be ported without the need of using the Oauth2 token.
