Wix connector — Headless API key + site selection

Wix's API uses a single Headless API key per account, scoped to one or more sites. Each Wix product (Stores, Bookings, Events, Members, Forms, Data) is a separate permission you tick when generating the key. The Insites migration only reads — Studio never writes back.

Generate the API key#

1. Sign in at manage.wix.com

   Sign in at manage.wix.com with the account that owns the site.

2. Open the API Keys section

   Open the account dashboard (top-left avatar → Account Settings → API Keys), then click Generate API Key.

3. Set the permissions

   Name it Insites Studio. Under Permissions, tick Read for each Wix product the site uses (see table below).

4. Pick the site

   Under Sites, select the specific site to migrate. Wix keys can be account-wide or per-site — per-site is safer.

5. Copy the key

   Generate, copy the key, and paste it into the connector form along with the site ID (visible in the dashboard URL after /dashboard/).

Permissions by Wix product#

Tick Read on every Wix product the site uses. The connector skips silently when a product isn't enabled, so you can't accidentally over-pull, but anything missed here is data the migrated site will be missing.

Product	Module	Why we need it
Wix Stores	Ecommerce	Products, collections, inventory, orders. Required for any Wix store. Without it, the migrated site has no catalog and no order history.
Wix Members	CRM	Site members and their profiles. Becomes Insites CRM contacts. Required for any site with logged-in members.
Wix Bookings	Ecommerce	Service offerings and past bookings. Required for any service-based site (clinics, classes, salons). Skip if the site has no bookings.
Wix Events	Ecommerce	Events, ticket types, and registrations. Skip if the site doesn't sell tickets.
Wix Forms	Forms	Form submissions captured through Wix's built-in forms. Without it, lead history collected through the contact page is lost.
Wix Data (Collections)	Data	Custom database collections built in Wix Studio's CMS. Becomes Insites Data module records. Critical for any site that uses dynamic pages.

Don't grant these#

Permission	Why
Manage permissions	Studio only ever reads. Don't grant any "Manage" permission. If the API key UI only offers a single "Manage" tier for a product family the site doesn't use, leave it off entirely.
Site analytics	Wix-generated reports — not data the new site needs. Recreate analytics natively in Insites or via a third-party tag.
Billing / Account info	Wix billing data is irrelevant to a migration. Don't share it.

Wix Studio versus classic Wix#

The same connector works for both Wix Editor (classic) and Wix Studio sites. Studio sites usually expose more data through Wix Data (collections), since that's where Studio's dynamic pages live. Classic Editor sites are mostly static HTML — for those, the migration leans more on the storefront crawler than the API.

Wix doesn't expose the Editor's design tokens through the API. Layout and typography are recreated from the rendered HTML.

Token storage (alpha)#

The API key is kept in your browser's localStorage so a refresh or shared link doesn't lose the migration session. It's sent to the Insites server only at the moment of a connection test or import run, and is never logged. Before GA we'll switch to a server-side token exchange so the key never touches the browser.

Revoke the key from the Wix dashboard after the migration completes — see other connector guides.