# Etsy setup for PopMCP You end up pasting your Etsy app's Keystring (the OAuth client id) and its Shared Secret from the Etsy Developer Portal into PopMCP. - Auth: OAuth authorization - Setup time: 10 min, plus Etsy's app review - API base URL: https://api.etsy.com/v3 - Credentials screen: https://www.etsy.com/developers - Provider docs: https://developers.etsy.com/documentation/essentials/authentication/ ## Approval required before this works Which gate you hit depends on app type. Etsy's docs say Seller Apps are approved automatically for eligible sellers, but a Personal App "goes through a deeper review process than Seller Apps", and serving sellers at production scale needs a separately reviewed Commercial Access upgrade. - Typical wait: Seller App: Etsy states eligible sellers are "approved within minutes, with no manual review queue". Personal App and Commercial Access: Etsy publishes no figure and says only that "Commercial Access requests are reviewed manually. Review time may vary depending on your proposed use case." Developers in Etsy's own community forums report waits of several days to several weeks, with 20+ days per attempt not unusual. - Cost: Free. Etsy charges nothing for registration, review, or the Commercial Access upgrade. - Blocked until approved: Until the app is approved the keystring is inactive and every request fails, so no OAuth consent screen, no listings, orders, inventory, or shop data. An approved Seller App is still scoped to your own shop only. A Personal App works for other sellers at limited scale; serving sellers at production scale requires the Commercial Access upgrade. - Works meanwhile: If you are an active Etsy seller in good standing, register a Seller App: eligible sellers are approved within minutes with no manual review queue, and that key works immediately against your own shop. Build and test the entire integration on it while the Personal App or Commercial Access request is pending. ## Before you begin - An Etsy account signed in to etsy.com - An Etsy shop if you register a seller app, since seller apps only reach your own shop - Acceptance of the Etsy API Terms of use - Etsy approval. Every app is reviewed before its keystring goes live. Seller apps get a light review. Personal and commercial apps get a deeper one. ## Get your credentials ### 1. Open the Etsy Developer Portal and pick an app type Sign in at etsy.com/developers to land on the Dashboard. Click Get started under Create a seller app if the connection only touches your own shop, or under Create a personal app if it needs to reach beyond it. Screen: https://www.etsy.com/developers/ ### 2. Register the app Fill in what you are building and how you will use the API, then tick the box accepting the API Terms of use. Name the app `PopMCP` and click Register to submit it for review. The seller form sits at `etsy.com/developers/register-seller-app` and the personal one at `etsy.com/developers/register`. Screen: https://www.etsy.com/developers/register-seller-app ### 3. Wait for the app to be approved Return to the Dashboard and check the app's row. Wait until its status reads Approved. Screen: https://www.etsy.com/developers/ ### 4. Copy the keystring and reveal the shared secret Open the approved app from Your Apps and copy the Keystring. Click the visibility icon next to Shared Secret, then copy that value too. Screen: https://www.etsy.com/developers/your-apps ### 5. Register PopMCP's callback URL, then paste both values On the app's Callback URLs tab, add the callback URL PopMCP prints on its Etsy connect screen, character for character. Paste the keystring into API Key (keystring) and the secret into Shared Secret in PopMCP, then click connect. Screen: https://www.etsy.com/developers/your-apps ## Fields PopMCP asks for - Auth type (connectionType): Create an app at etsy.com/developers/your-apps. Etsy uses PKCE, so no client secret is sent during sign-in. Your Etsy login stays on Etsy's side. - API Key (keystring) (clientId) [required]: Your app's "Keystring" from etsy.com/developers/your-apps. This is the OAuth client id. - Shared Secret (sharedSecret) [required]: Your app's Shared Secret (same page as the keystring). Etsy requires it in the x-api-key header on every request. Stored encrypted; used server-side only. ## Callback URL to register https://app.popmcp.com/api/providers/etsy/callback ## Scopes requested - shops_r - shops_w - listings_r - listings_w - listings_d - transactions_r - transactions_w - address_r - email_r ## Verify The Etsy connector in PopMCP flips to Connected and shows your shop name, and a shop or listings tool returns your real listings. ## Troubleshooting ### 403 on every call right after registering Cause: The app has not been approved yet, so the keystring is inactive. Fix: Check the app's row on the Developer Portal Dashboard and wait until it reads Approved. ### invalid_api_key or 401 from the token endpoint Cause: The shared secret was copied while still masked, or the keystring and secret came from two different apps. Fix: Reveal the shared secret with the visibility icon and re-copy both values from the same app page. ### redirect_uri mismatch during sign-in Cause: PopMCP's callback URL is not registered on the Etsy app, or it differs by a trailing slash or by http versus https. Fix: Copy the callback URL exactly as PopMCP prints it into the app's Callback URLs list. ### 429 Too Many Requests Cause: The app exceeded its Queries Per Second or Queries Per Day allowance. Fix: Honour the retry-after header, then email developer@etsy.com with your use case to request higher limits. ### Seller app cannot see another shop's data Cause: Seller apps are scoped to the registering account's own shop by design. Fix: Register a personal app instead, and request an upgrade to commercial access if you need more scale. ### Every request fails with a malformed key error Cause: Only the keystring was sent in the x-api-key header. Fix: Etsy v3 wants keystring and shared secret joined by a colon. Confirm both fields are filled in PopMCP. --- Source: https://www.docs.popmcp.com/docs/integrations/etsy/