OAUTH / MINIMUM ACCESS
How the Etsy connection works.
Authorization happens on Etsy. The application receives an access token limited to the permissions granted by the seller.
Authorization
When a seller chooses to connect a shop, the seller is redirected to Etsy to review the requested permissions. Etsy returns an authorization result to the application; the seller's Etsy password is not provided to this application.
| Scope | Why it is needed | V1 |
|---|---|---|
listings_r | Display the connected shop's own active and draft listings and the listing information required by the workspace. | Requested |
listings_w | Create one seller-confirmed draft and attach the selected images and inventory payload. | Requested |
shops_r | Read relevant private shop information and shipping configuration required to complete listing forms. | Requested |
listings_d | Deletes listings. V1 does not delete listings. | Not requested |
shops_w | Changes shop-level settings. V1 does not change these settings. | Not requested |
Authorization sequence
The seller starts the connection in this application, reviews the requested scopes on Etsy, and returns to the exact registered callback. The server exchanges the authorization code using PKCE and associates the resulting token with the correct application user and authorized shop.
Token use
OAuth tokens stay on the server, are encrypted at rest using AES-GCM, and are used only to perform authorized functions for the connected shop. Access tokens are refreshed only through Etsy's token endpoint. Tokens are not sold, transferred to another application or exposed in the browser.
Scope changes
If the application later needs a different scope, the product disclosure and Etsy application purpose must be reviewed and the seller must complete authorization again. V1 does not silently expand access.