Etsy connection

Every permission, and why it is needed

Fablenco reaches your shop only through Etsy Open API v3, and only with the permissions you approve on Etsy’s own consent screen. This is the complete list.

Requested scopes

listings_r

read
Why it is necessary
Read the connected shop's own listings, inventory, images, video and personalization settings.
Where it is used
Listing list and editor, product library, bulk editor

listings_w

write
Why it is necessary
Create draft listings and update the connected shop's own listings, images, video, inventory and personalization.
Where it is used
Product Creator, listing editor, bulk editor

shops_r

read
Why it is necessary
Read the shop's own shipping profiles, return policies, processing-time profiles and shop sections.
Where it is used
Required fields when a draft is created

shops_w

write
Why it is necessary
Create a shipping profile, return policy, processing-time profile or shop section in your own destination shop when a product is copied into a shop that has no matching one yet. Shown and confirmed first.
Where it is used
Copy a product into another of your own shops

transactions_r

read
Why it is necessary
Read the shop's own receipts to show the order list, order detail, ship-by date and the shop's own sales and fee figures.
Where it is used
Orders, order detail, reports

transactions_w

write
Why it is necessary
Write the carrier and tracking number you enter when you mark one of your own orders as shipped.
Where it is used
Mark as shipped

Scopes we do not request

  • listings_d — The application never deletes a listing.
  • address_r — Shipping details are only read as part of your own shop's receipt; no separate address scope is used.
  • email_r — The application does not read member email addresses.
  • profile_r / profile_w — The application does not read or change your Etsy member profile.
  • favorites_r / feedback_w / cart_r / billing_r / recommend_r — No implemented feature uses them.

Buyer email addresses are not part of this application. Etsy requires a separate request for the buyer_email field, and we have not asked for it and do not use it.

You are the one who grants access

When you connect a shop you are sent to Etsy. Etsy signs you in and lists the permissions being requested, and you approve or refuse them there. If you refuse, no token is issued and the application cannot see anything. We never ask for your Etsy password, your API keystring or your shared secret, and there is nowhere in the application to type them.

How the connection stays alive

Etsy issues a short-lived access token and a refresh token. Both are kept on our server. When the access token is about to expire, our server asks Etsy for a new one using the refresh token — you are not asked to sign in again, and no credential ever passes through your browser. If you disconnect, or revoke the application on Etsy, the stored tokens stop working and are deleted on our side.

How to disconnect

  • In the application: open the shops page, choose the shop and use the disconnect action. The shop’s access token, refresh token and cached Etsy data are deleted at that moment.
  • On Etsy: in Etsy’s Shop Manager you can revoke this application’s access under your account’s connected-app settings. After that, any call we make is refused by Etsy.
  • Everything: to delete your application account and all the data belonging to it, write to support@fablenco.com.

Limits we work inside

  • Listing content shown to you is refreshed from Etsy inside Etsy’s freshness window; supporting data is cached for at most 6 or 24 hours depending on the kind.
  • Etsy’s per-second and rolling daily request limits are respected, and a rate-limit response is retried with bounded backoff rather than immediately.
  • Every read and write described on this site uses documented Open API v3 endpoints — no internal and no legacy endpoints.

The term 'Etsy' is a trademark of Etsy, Inc. This Application uses Etsy's API, but is not endorsed or certified by Etsy.