Ecwid
Connect Ecwid to manage products, variations, orders, customers, categories, discount coupons, and store settings.
You end up pasting your numeric Ecwid store ID and the secret token from your custom app's Details page into PopMCP.
Paid plan required before this connector works
Ecwid exposes its REST API only to stores on a paid plan - the docs state plainly that 'Only stores on paid plans can access API', so a free store cannot use the API no matter how the custom app is configured. There is no review or application for the API itself.
- Typical wait
- None for the API itself - upgrading the plan enables it immediately. Changes to an app's access scopes are handled by Ecwid API Support 'in 24 hours or less' on business days.
- Cost
- A paid Ecwid plan (the free plan is excluded; Ecwid does not publish a per-tier API mapping, so check the current plan page before committing). Ecwid grants a free upgrade to a paid plan for developers building a store customization, an integration for a working store, a public App Market app, or Instant Site templates - you email API Support to request it. Creating the custom app and its tokens is free.
- Blocked until approved
- Every REST call. On a free store, plan-gated calls come back as HTTP 402 NOT_AVAILABLE_ON_CURRENT_PLAN, so nothing - products, orders, customers - can be read or written. There is also no test mode in the Ecwid API, so Ecwid recommends a separate test store rather than experimenting against a live one.
- Works meanwhile
- On any paid store there is nothing to wait for: opening the app dashboard auto-generates your first custom app with default scopes (read/write products and categories, read store profile, read/change placed and unfinished orders) and both a public and a secret access token immediately.
Where to apply: No form for the API itself - upgrade the store in the Ecwid admin (or email API Support for the free developer upgrade if you qualify). Then open the app dashboard at my.ecwid.com/#develop-apps and copy the secret token from the custom app's Details page. Scopes and endpoint URLs beyond the defaults are requested via 'request application update' from the Ecwid admin.
- Requesting extra access scopes is a manual, human step: Ecwid API Support turns app-configuration updates around in 24 hours or less on business days, and you must reinstall the custom app afterwards to be issued tokens carrying the new permissions.
- Webhook automations and similar features need self-hosted endpoint URLs ready at the time you request the app update - prepare them first or the request stalls.
- The public token only reads public data; anything meaningful needs the secret token, which must never ship in client-side code.
- There is no sandbox or test mode - develop against a separate test store (the free developer plan upgrade exists precisely for this).
- A custom app is single-store by design - it cannot be installed on another merchant's store. Distributing to other Ecwid stores means a public App Market app, which does go through Ecwid app validation.
- Ecwid stores sold under white-label brands (Lightspeed eCom C-Series and similar) use the same API but different admin URLs, which trips up setup instructions.
- Setup time
- 6 min
- Auth
- API credentials
- API base URL
- https://app.ecwid.com/api/v3/{storeId}
Before you begin
- A paid Ecwid plan. The REST API is not available on the Free plan
- Store owner access, or a staff account with full control panel access
- A custom app on the store. Ecwid creates one automatically the first time you open the app dashboard at my.ecwid.com/#develop-apps
- For anything beyond the default permissions, a scope request emailed to Ecwid API support before the extra scopes appear on the app
Get your credentials
Open the app dashboard
Sign in to the Ecwid control panel and open Apps → Develop apps, or go straight to my.ecwid.com/#develop-apps.
Develop apps
Custom apps that give this store API access.
| Application | Type | Status | Created |
|---|---|---|---|
| Acme Supply Co custom appcustom-app-****-3f9a | Custom | Installed | Mar 4, 2026 |
Ecwid generates your first custom app automatically the first time this page loads.
Open the app's Details page
Click the custom app and open its Details page. Click Install first if the app is not installed on this store.
Details
All settings on this page are read-only.
- client_id
- custom-app-****-3f9a
- client_secret
- ****
- Store ID
- 10012345
Reinstalling the app issues new tokens and invalidates the old ones.
Copy the secret token
In the Access tokens section copy the value next to Secret token. Ignore Public token, it only reads public storefront data.
Details
All settings on this page are read-only.
- Public token
- public_9dQ****WsGg
- Secret token
- secret_EZWi****NBBM
Access tokens do not expire and are tied to this one store.
Read your store ID
Take the numeric Store ID from the footer of any Ecwid admin page, or from an admin URL such as my.ecwid.com/store/10012345.
Paste both values into PopMCP
In PopMCP put the number into Store ID and the secret_ value into Secret token, then click Connect.
Connect in PopMCP
Open your workspace, choose Ecwid in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| Store IDtext | Your numeric Ecwid store ID, shown in the Ecwid admin footer and in admin page URLs. Paste just the number, or an admin/API URL that contains it; we'll pull it out. |
| Secret tokensecret | Ecwid control panel → Apps → develop apps (my.ecwid.com/#develop-apps) → open your custom app → Details → copy the secret token. It grants full REST access (per the app's permissions) and does not expire. Stored encrypted; used server-side only. Note: the Ecwid REST API requires a paid Ecwid plan.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Ecwid immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
The Ecwid card in PopMCP flips to Connected, and a test call such as 'list products' returns items from your catalog.
Troubleshooting
401 Unauthorized
Why: You used the public token, or the token belongs to a different store.
Fix: Copy the Secret token from the Details page of the app installed on this exact store. Tokens are per store.
403 Forbidden on a specific call
Why: The custom app does not hold that access scope.
Fix: Email Ecwid API support to add the scope, reinstall the app, then reconnect with the newly issued secret token.
Token stopped working suddenly
Why: The app was uninstalled and reinstalled, which regenerates both tokens.
Fix: Copy the new secret token from the Details page and update the PopMCP connection.
'Store not found' or 404
Why: Wrong store ID.
Fix: Re-read the store ID from the admin page footer, or paste an admin URL and let PopMCP extract the number.
The Develop apps page offers no API access
Why: The store is on the Free plan.
Fix: Upgrade to any paid Ecwid plan, then reopen the app dashboard.