AutoGineer
Generated banner for Wix Headless
Generated logo for Wix Headless

Wix Headless

WixOfficialPublished by Wix

  • Skill
  • Tool integration
  • Software development
  • MIT
  • Low risk
  • Has scripts
Download ZIP

From the author

Connect Wix business services (Stores, Bookings, Donations, CMS, Blog, Events, Forms, and more) to a Wix Headless frontend — infer the needed capabilities, install the apps, seed backend content, and produce an SDK-integration guide. For managed (Wix-hosted) projects it can also build the frontend: scaffold a new site (create) or wire an existing/brought-in design (connect), then build and release. Works across managed, self-managed, and stripe project types. Triggers: set up a Wix Headless backend, add Wix business features to my app, accept donations, build or host a Wix site, connect/implement this design with Wix.
— the description by Wix

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The wix-headless skill acts as an orchestrator for integrating Wix business services (such as Stores, Bookings, and CMS) into a headless frontend architecture. It handles the end-to-end configuration of the Wix backend, including app installation, content seeding, and the generation of a tailored SDK integration guide. Depending on the project type (managed, self-managed, or stripe), the skill can either provide a comprehensive integration guide for the user to implement or, in managed scenarios, actively scaffold, wire, and deploy the frontend project.

What it does

  • Infers required Wix capabilities based on user intent and project context.
  • Installs necessary Wix apps and seeds backend content automatically.
  • Generates a custom SDK integration guide for calling Wix services from the frontend.
  • Scaffolds or connects existing frontend projects to Wix for managed hosting.
  • Handles project-type-specific authentication and deployment workflows.
  • Provides a mechanism to relay feedback to Wix regarding the headless experience.

When to use it

  • When you need to integrate Wix business services into a custom-built headless frontend.
  • When you want to automate the setup and content seeding of a Wix backend.
  • When you are building a new site on Wix infrastructure and need a scaffolded frontend.
  • When you have an existing frontend design and need to wire it to Wix business capabilities.
  • When working with Stripe Projects and requiring a Wix backend configuration.

Advantages

  • Reduces manual configuration by automating app installation and content seeding.
  • Provides a clear, actionable SDK integration guide tailored to your specific capabilities.
  • Supports multiple project architectures including managed, self-managed, and Stripe-based setups.
  • Ensures consistent backend setup by following verified inline recipes.
  • Simplifies the transition from design to a functional, Wix-powered headless site.

Usage examples

“Set up a Wix Headless backend for a store with products and a blog.”
The skill will install the Stores and Blog apps, seed sample products and posts, and provide an SDK guide for fetching this data in your frontend.
“I have an existing design; connect it to Wix and host it on their managed infrastructure.”
The skill will initialize the project, wire the existing UI to the necessary Wix business services, and prepare it for release on Wix.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/wix/wix-headless/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip wix-headless.zip -d .agents/skills

Documentation by Wix

Wix Headless

This skill connects Wix business services to a Wix Headless frontend. Its core job is to configure the Wix backend: infer the needed capabilities, install the Wix apps, seed the backend content, and produce an SDK-integration guide describing how to call Wix from the frontend.

What happens with the frontend depends on the project type and operation:

  • Backend-only (self-managed, stripe, or a managed "just set up the backend" run) — the skill emits the SDK guide as its final output; the host owns the frontend, build, and hosting.

  • Managed create / connect — the skill also owns the frontend: it scaffolds a new project (create) or attaches Wix to an existing one (connect), wires it to the backend using that same guide, builds, and releases to Wix. (There is no Designer or template library — the frontend is built ad-hoc to intent.)

On a backend-only run the skill does not own the project scaffolding. When the work needs a frontend, scaffold it according to user intent — framework and structure follow the prompt; the skill's job is the Wix backend plus the emitted SDK guide describing how to call Wix from whatever frontend exists, not choosing or generating the app. This is the norm for a stripe run: the project is provisioned via Stripe Projects (credentials land in .env — see stripe/AUTHENTICATION.md), the skill configures the backend and emits the guide, and the live site is finalized per stripe/DEPLOYMENT.md — while the frontend is scaffolded and wired to intent, by the host.

Project types

The skill behaves identically across project types except for authentication and deployment, which are isolated in a per-type folder under references/:

Project typeHostingAuthentication & deployment live in
managedWix infrastructure (maintained by Wix)references/managed/
self-managedthe user's own host (TBD)references/self-managed/
stripethe user's own host, provisioned via Stripe Projectsreferences/stripe/

Everything else — Discovery, Setup, Seed, the SDK handoff — is project-type-agnostic and refers to "the provided authentication mechanism" rather than any specific method.

Resolving the project type

Resolve the type before Discovery, in this order — stop at the first that decides:

  1. Caller-provided. If the host/caller passed a project type (managed | self-managed | stripe), use it. An explicit value always wins.

  2. Detect from project signals (on disk). Check the working directory (read-only):

    • stripe — .env carries WIX_WIX_CLIENT_ID / WIX_WIX_CLIENT_SECRET / WIX_WIX_METASITE_ID (or the plain WIX_* fallback). This is the Stripe-Projects fingerprint.

    • managed — a Wix CLI project: wix.config.json present, or a .wix/ directory, or @wix/cli / @wix/astro in package.json.

    • self-managed — a frontend project on disk (e.g. package.json with a bundler/framework) with neither the Stripe .env fingerprint nor the Wix-CLI markers above.

  3. Detect from user intent. If disk is inconclusive, read the prompt:

    • managed — "managed", "host on Wix", "Wix-hosted", "deploy to Wix", "wix release".

    • stripe — "stripe projects", "I added Wix via Stripe", a Stripe-Projects context.

    • self-managed — "self-hosted", "my own host", names a non-Wix host, "I'll deploy it myself".

  4. Ask. If signals are absent or conflict, ask the user which type applies — don't guess.

Hold the resolved type in scratch; it selects <TYPE_DIR> (see Path resolution). Note self-managed is TBD — once resolved to it, the auth step will stop with a clear "not wired yet" error.

Resolving the operation (managed only)

create/connect/iterate are managed-only. For managed, resolve the operation by intent first, directory second — never let an empty directory override what the user is asking for. Check iterate first (it's decided by an unambiguous on-disk signal):

  • iterate → references/managed/CONNECT.md. The project is already connected to Wix — a wix.config.json (or .wix/) is already present — and the owner wants to add or change capabilities. Same flow as connect, but §1 skips init and reuses the existing wix.config.json; never re-init an already-connected project.

  • connect → references/managed/CONNECT.md. The user brings a design not yet connected to Wix and wants it wired: a frontend project on disk without a wix.config.json, or a brought-in/fetched design (a .zip/folder/file you unzip or read, a design-file URL, a Claude-Design/v0/Lovable export), or language like "connect this / implement this design (… connecting to Wix) / host this on Wix / deploy this to Wix / add Wix Headless to this project". A brought-in or fetched design is connect even when the current directory is empty — the design arrives from elsewhere (zip/fetch/URL), so emptiness at trigger time is not a create signal. (CONNECT.md step 1 places the brought design into CWD, then inits it.)

  • create → references/managed/CREATE.md. The user wants a new site built from a prompt with nothing brought in — "build me a site / store / blog…", no design file, no project on disk.

  • backend-only — the user only wants the backend configured (no frontend work). → the shared spine + emit the SDK handoff.

For self-managed and stripe, the operation is always backend-only (the host owns the frontend). Only when there is genuinely no brought-in design and no connect language does directory emptiness decide: empty → create; an existing frontend on disk → connect.

Preconditions (the host provides these — we read, never create)

  1. The project type — managed | self-managed | stripe — provided by the caller, else detected from project signals / user intent (see Project types § "Resolving the project type"), else asked. It selects <TYPE_DIR> (see Path resolution).

  2. A Wix metasite + a headless OAuth app exist, and credentials are available — obtained via the project type's AUTHENTICATION.md. The skill needs a bearer token authorized for the metasite and the metasite id.

  3. The user intent — free text describing what Wix should power ("add a store", "blog + contact form", "persist my app's data").

  4. (Optional) the project on disk — read-only, to sharpen brand/capability inference.

If the credentials are absent, the Wix backend isn't reachable — stop with a clear error.

What this skill does

Always open DISCOVERY.md first (it's agnostic — capability/brand/intent inference + the imagery gate, no auth). Then route by project type + operation:

Backend-only (self-managed, stripe, or managed backend-only) — the lean spine:

  1. Discovery (references/DISCOVERY.md) — infer capabilities + brand + intent + imagery.

  2. Setup (references/SETUP.md) — install the Wix apps those capabilities need.

  3. Seed (references/SEED.md) — create the backend content (+ entity images if imagery is on).

  4. Handoff (references/SDK_HANDOFF.md) — after Setup and Seed, emit the integration guide: SDK bootstrap, per-capability call shapes, the seeded IDs, and the @wix/* package list.

  5. Finalize deployment (<TYPE_DIR>/DEPLOYMENT.md) — run the project-type's finalize steps.

Throughout any run — if the user asks to send feedback to Wix, complains/gets frustrated, or the run hits any real friction (a confusing error, a doc gap, a tooling dead end, a workaround you had to invent — it doesn't need to repeat), offer to relay it to Wix per references/FEEDBACK.md. Default to offering rather than waiting to be asked. Every flow's finalize step (<TYPE_DIR>/DEPLOYMENT.md / managed/CREATE.md / managed/CONNECT.md) ends with the same checkpoint — treat it as a required self-check, not optional. Send only after an explicit yes — never automatically.

Managed create / connect / iterate — after Discovery, hand the whole run to the managed flow:

  • create → references/managed/CREATE.md (scaffold → Setup → Seed → build the frontend → release).

  • connect → references/managed/CONNECT.md (init → Setup → Seed → wire the existing UI → release).

  • iterate → references/managed/CONNECT.md — the project is already connected, so it reuses the existing wix.config.json (no init). Setup / Seed / wiring are incremental: it may already be set up and seeded from a prior run, so the agent checks current state first (installed apps, already-seeded content, existing wiring) and applies only the delta the new intent needs — never blindly re-installing or re-seeding. Re-release only if the frontend build output changed. These reuse the same SETUP.md/SEED.md/SDK_HANDOFF.md, but apply the SDK guide to build/wire the frontend themselves rather than emitting it, and release via managed/DEPLOYMENT.md.

Each Wix call uses the universal call shape (SETUP.md §1) with $TOKEN/$SITE_ID obtained per <TYPE_DIR>/AUTHENTICATION.md. The skill runs non-interactively except for the one imagery question (and asking the project type if it can't be resolved).

Don't smoke-test the frontend locally unless the user asks to verify. The deliverable is the built-and-released site (managed) or the SDK guide (backend-only) — not a local test report. By default do not start a dev server (wix dev / astro dev / npm run dev) to curl pages, drive the cart / booking / login flow, or launch a headless browser: correctness comes from following the recipes, real errors surface at wix build / wix release, and a headless run can't complete an interactive login or a real payment anyway — so these loops routinely burn minutes of wall for little signal (this is distinct from, and in addition to, the "release once at the very end" rule — that one only bans extra build+release cycles, not dev-server testing). Only spin up a dev server and smoke-test when the user's prompt explicitly asks to verify / test / confirm it works — and then keep it to a single lightweight pass (pages compile and render), not a full purchase/booking/login drive. The one post-release check in <TYPE_DIR>/DEPLOYMENT.md is the sanctioned verification.

Donations exception to the smoke-test policy above: for a build that accepts donations, follow the bounded anonymous API handoff check in references/inline-recipes/how-to-code-donations.md before claiming it works. It does not authorize a payment or campaign mutation, and does not require a dev-server testing loop. That recipe also defines the separate hosted-checkout and payment checks.

Path resolution

Compute <SKILL_ROOT> from this file (<SKILL_ROOT>/SKILL.md — strip /SKILL.md); hold the absolute path in scratch. Then resolve the project type to its folder and hold it too:

<TYPE_DIR> = <SKILL_ROOT>/references/<projectType>/ — one of managed/, self-managed/, stripe/.

WhatPath
Vertical index (intent matching + per-vertical site spec)<SKILL_ROOT>/references/CAPABILITIES.md
Discovery (infer capabilities + brand + intent; existing site → the Dynamic Context call in §1)<SKILL_ROOT>/references/DISCOVERY.md
Setup (install apps)<SKILL_ROOT>/references/SETUP.md
Seed (create backend content)<SKILL_ROOT>/references/SEED.md
SDK-integration handoff (emitted, or applied by create/connect)<SKILL_ROOT>/references/SDK_HANDOFF.md
Image generation (opt-in; agnostic)<SKILL_ROOT>/references/IMAGE_GENERATION.md
Design — fallback visual quality bar for the built frontend, when the user gave no design direction of their own (managed create only)<SKILL_ROOT>/references/DESIGN.md
Content — fallback copy quality bar for the built frontend, when the user gave no copy/voice direction of their own (managed create only)<SKILL_ROOT>/references/CONTENT.md
Experience overlays — a vertical's own design + copy bar on top of DESIGN/CONTENT (optional per vertical; read when that vertical is loaded)<SKILL_ROOT>/references/inline-recipes/experience-<vertical>.md (today: experience-store.md, experience-donations.md)
AI features — text/chat + embeddings (opt-in; agnostic)<SKILL_ROOT>/references/AI_FEATURES.md
Feedback — relay the user's headless-experience feedback to Wix (opt-in; user-approved)<SKILL_ROOT>/references/FEEDBACK.md
Authentication — obtain $TOKEN/$SITE_ID/clientId (project-type-specific)<TYPE_DIR>/AUTHENTICATION.md
Deployment — finalize the live site (project-type-specific)<TYPE_DIR>/DEPLOYMENT.md
Managed create flow (scaffold a new project)<SKILL_ROOT>/references/managed/CREATE.md
Managed connect flow (wire an existing project)<SKILL_ROOT>/references/managed/CONNECT.md
Frontend-axis references (how a frontend wires to Wix)<SKILL_ROOT>/references/astro.md, non-astro.md

Start a run by opening DISCOVERY.md. The flow files (CAPABILITIES, DISCOVERY, SETUP, SEED, SDK_HANDOFF, IMAGE_GENERATION, AI_FEATURES) are project-type-agnostic; the per-type specifics live under <TYPE_DIR>/ (AUTHENTICATION.md, DEPLOYMENT.md, and — managed only — CREATE.md/CONNECT.md).

Where the how comes from

This skill has no skill upstream — the how is read from the live Wix docs at dev.wix.com/docs. Read-priority: a page this skill links is read by curl-ing its .md twin directly (first priority — don't re-discover a curated link with search); the Wix MCP doc/search tools are second priority, for finding pages the skill doesn't link or as a fallback if a fetch fails. (Append .md to any docs URL for raw markdown; menu pages list child links, content pages carry the schema.)

Doc discovery is the shared fallback for both tracks — never the first move. Each track's primary source is its pinned material (below); when that doesn't cover what you need, fall back to references/DOC_DISCOVERY.md — a semantic doc-search + schema lookup that works with or without the Wix MCP.

  • Seed reads each capability's create flow from its inline recipe — a self-contained local inline-recipes/setup-*.md (mapped per capability in SEED.md § "What to seed per capability") that inlines the calls and supersedes the REST doc pages, so read it and seed from it alone. Only a capability with no inline recipe (e.g. coupons) falls back to doc discovery (DOC_DISCOVERY.md).

  • Handoff links the SDK docs for each capability's API shape, and supplies the runtime package set from the inlined map in SDK_HANDOFF.md (the SDK .md pages don't expose @wix/* import strings to navigation, so packages are mapped, not navigated).

Setup carries its app-install call (and the appDefId constants) inline in SETUP.md; CAPABILITIES.md is the vertical index that lets Discovery match intent and declares, per built vertical, the Required site features + Implementation checklist that Seed enables (backend-backed features) and the Handoff carries into the guide (so the host builds a complete site, not a bare data dump). This skill carries the what (which capabilities, how much content, what a finished site includes) and reads the how off the docs.

Files

references/inline-recipes/how-to-code-members-custom-login.md

name: "How to Code Members (custom login page)" description: The frontend contract for a custom, branded login/sign-up page — you build the UI and drive Wix's auth service directly with the OAuthStrategy SDK (register / login / processVerification / getMemberTokensForDirectLogin / setTokens / sendPasswordResetEmail / logout), instead of redirecting to the Wix-hosted login page. This is the surface to use only when the brief asks for a custom/in-app login form or custom sign-up fields (name, address, username, arbitrary fields); otherwise use the Wix login page (how-to-code-members-*.md). Covers the loginState state machine (SUCCESS / EMAIL_VERIFICATION_REQUIRED / OWNER_APPROVAL_REQUIRED / FAILURE), custom profile fields at sign-up, token persistence, reading the member with @wix/members, and the no-auth.elevate rule. Works on any headless project (managed or self-managed) — the choice is intent, not project type.

RECIPE: How to Code a Custom Login Page (branded in-app auth, OAuthStrategy register/login, @wix/members)

A concise contract for building your own login / sign-up / logout UI and driving Wix's authentication service directly — instead of bouncing the visitor to the Wix-hosted login page. This is the how (which SDK calls, which states, which failure modes), not the what — the form design, which pages are gated, and what the account page shows come from the request you're fulfilling.

⚠️ WHEN TO USE THIS RECIPE — intent, not project type. Reach for custom login only when the brief explicitly asks for it: a branded / in-app login form (the visitor never leaves your UI) or custom sign-up fields (full name, username/nickname, address, arbitrary fields). If the brief just says "let members log in / sign up / have an account" with no mention of a custom form or extra fields, use the Wix login page instead — how-to-code-members-astro.md (Astro) or how-to-code-members-non-astro.md (non-Astro). The Wix login page needs zero UI and is the deterministic default; custom login is more code and more failure modes, so take it on only on real intent.

Works on any headless project. The Wix docs frame custom login pages as "self-managed only," but that's positioning, not a technical lockout — the register/login SDK methods (and their Register V2/Login V2 IAM endpoints) authenticate against the same Wix auth service and work on managed projects too. So do not branch on project type — if the intent is custom login, build it; the flow below is identical on managed and self-managed.

One client, one flow — sign-up and log-in are the same machine. Both register() and login() return the same StateMachine shape and both end at getMemberTokensForDirectLogin → setTokens. Member tokens are the same shape as visitor tokens (role: member); logging in just swaps the token set on the visitor client you already have.

⚠️ This is a client-driven (OAuthStrategy) flow — it is the non-Astro shape. register/login live on client.auth, i.e. the manual visitor client non-astro.md builds. Astro's auto-auth ships no client to call them on. So: on a non-Astro frontend (SPA / static), this is the natural path. On Astro, custom login means stepping outside auto-auth — instantiate an explicit OAuthStrategy client (in a backend route or a client island) to run these calls; do not expect the built-in /api/auth/* routes to do custom login (they only drive the Wix login page). If the brief is Astro and doesn't demand a custom form, prefer the Wix login page (how-to-code-members-astro.md).

Pinned docs (read before wiring — curl the .md directly):

Preconditions

  • clientId only, never the secret. Custom login uses the same public OAuth client id as the visitor client (non-astro.md N6). No client_secret in the frontend, ever.

  • No redirect / no allow-listed callback for login itself. Unlike the Wix login page, register/login are direct API calls — the visitor never leaves your page, so there is no redirectUri to allow-list for the login round-trip. (Two side flows do redirect and need an allow-listed URI: sendPasswordResetEmail(email, redirectUri) and logout(originalUrl)'s logoutUrl. Allow-list those URLs on the OAuth app if you wire password reset / logout return.)

  • The visitor session is automatic. The client mints an anonymous visitor token on first use, and register/login run under it — you do not hand-mint a visitor token first. (That manual step only exists in the raw-REST version of this flow.)

  • Profile data still needs the Members Area app. Reading the member back (getCurrentMember) and defining customFields need the Wix Members Area app installed (SETUP.md) — see the identity-vs-profile split below.

Identity vs. profile — two layers, don't conflate them

  • Identity / auth — sign up, log in, log out, "is this caller a member?". Native to the headless OAuth app. No app install needed — the whole register/login/loggedIn() flow below runs on this layer alone.

  • Member profile / Members Area — reading name / photo / roles, an editable my-account page, and any custom field definitions. Served by the Wix Members Area app, which must be installed (SETUP.md). @wix/members getCurrentMember() returns data only once that app is present.

If getCurrentMember() is empty on a site where loggedIn() is true, suspect the Members Area app isn't installed — not a code bug.

The flow — build a form, call the SDK, handle the state machine

Reuse the one visitor client non-astro.md builds (createClient({ modules: { members }, auth: OAuthStrategy({ clientId }) })) — don't make a second client.

// Sign up — register() takes a `profile` for custom fields (this is why you'd pick custom login)
const res = await client.auth.register({
  email, password,
  profile: {                       // all optional; include what the brief's sign-up form collects
    firstName, lastName,
    nickname,                      // ≈ username
    addresses: [{ address: { /* … */ } }],
    // customFields: { <fieldName>: <value> }   // ⚠️ see note below — needs field defs
  },
});

// Log in — same StateMachine shape, no profile
// const res = await client.auth.login({ email, password });

// Handle the result (both register and login return this)
switch (res.loginState) {
  case 'SUCCESS': {
    const tokens = await client.auth.getMemberTokensForDirectLogin(res.data.sessionToken);
    client.auth.setTokens(tokens);   // subsequent SDK calls now run as the member
    persistTokens(tokens);           // see persistence below
    break;                           // now render the member UI / navigate
  }
  case 'EMAIL_VERIFICATION_REQUIRED': {
    // Wix has emailed a 6-digit code. Collect it in your UI, then:
    const v = await client.auth.processVerification({ verificationCode });
    if (v.loginState === 'SUCCESS') {
      const tokens = await client.auth.getMemberTokensForDirectLogin(v.data.sessionToken);
      client.auth.setTokens(tokens); persistTokens(tokens);
    }
    break;
  }
  case 'OWNER_APPROVAL_REQUIRED':
    // Membership is pending owner approval — show a "pending" notice; they can log in once approved.
    break;
  case 'FAILURE':
    // Surface a message keyed off res.errorCode:
    //   invalidEmail | invalidPassword | emailAlreadyExists | resetPassword
    //   | missingCaptchaToken | invalidCaptchaToken
    // 'resetPassword' → call sendPasswordResetEmail (below), don't retry login.
    break;
}

  • loggedIn() gates everything. client.auth.loggedIn() → false = anonymous, true = member. Render the account UI only when true; otherwise show your login form.

  • Logout is a redirect (same as the Wix-login path): const { logoutUrl } = await client.auth.logout(window.location.href); clearPersistedTokens(); window.location.href = logoutUrl;

  • Password reset: await client.auth.sendPasswordResetEmail(email, redirectUri) — redirectUri must be an allow-listed authorization redirect URI; Wix hosts the reset page and returns the member to it.

The loginState state machine — handle every branch (don't assume SUCCESS)

register() / login() / processVerification() all return a StateMachine ({ loginState, data: { sessionToken }, errorCode, error }). The trap is coding only the happy path:

  • SUCCESS — exchange data.sessionToken for tokens (above). Only here do you get a session.

  • EMAIL_VERIFICATION_REQUIRED — fires when a brand-new registrant's email already exists as a contact, or when email verification is enabled in the site's Member Settings. You must build the code-entry step (processVerification) or login silently dead-ends. With default settings + a fresh email, you'll usually get SUCCESS straight away — but code the branch anyway; it's site-setting-dependent, not code-dependent.

  • OWNER_APPROVAL_REQUIRED — signup policy is manual-approval; show "pending", don't treat as an error.

  • FAILURE — branch on errorCode (invalidEmail / invalidPassword / emailAlreadyExists / resetPassword / captcha codes). emailAlreadyExists on register = route them to log in; resetPassword = send a reset email.

Signup security (email verification, owner approval, reCAPTCHA) is dashboard-governed, not code. These are Site-Member-Settings toggles — document them as host-configurable, don't try to set them from a headless run. There is no headless TOTP/SMS 2FA; the security layers are password + email verification + reCAPTCHA. If reCAPTCHA is enabled in settings, pass captchaTokens to register/login (OAuthStrategy exposes captchaVisibleSiteKey/captchaInvisibleSiteKey).

Custom sign-up fields — the whole reason to pick this surface

register's profile (IdentityProfile) accepts firstName, lastName, nickname (≈ username), picture, phones, addresses, labels, language, privacyStatus, and customFields (an arbitrary name → value map). So "username + email + full name + address + password" maps straight onto profile.

  • ⚠️ Standard fields work as-is; arbitrary customFields need field definitions. firstName/lastName/nickname/addresses/phones are accepted directly. But keys inside customFields must first be defined via the Members Custom Fields API (which needs the Members Area app) — an undefined custom field is silently dropped. If the brief's extra fields are the standard ones, you need no field defs; only truly custom keys do.

  • The Wix login page cannot collect any of these — that's the capability custom login uniquely unlocks, and the reason to take on the extra code.

Token persistence & renewal — treat member tokens like visitor tokens

Member tokens are the same token set the visitor session machinery already handles; login just swaps them in.

  • Persist the token set (localStorage or a cookie) after setTokens so a reload stays logged in. On boot, if you have a stored set, client.auth.setTokens(stored) before first render — or pass tokens into OAuthStrategy({ clientId, tokens }) at client creation.

  • Renew with client.auth.renewToken(refreshToken) (or the SDK's automatic renewal when you re-hydrate via setTokens). A member session expiring is normal — refresh, don't force a re-login unless the refresh token is gone.

  • On logout, clear the persisted set so the next boot is a clean anonymous visitor.

  • Keep one shared client instance — creating a new client per component drops the session (a documented custom-login pitfall).

Read the current member — @wix/members, not the dev-preview package

import { members } from '@wix/members';
const { member } = await client.members.getCurrentMember({ fieldsets: ['FULL'] });
// member.profile?.nickname, member.profile?.photo, member.loginEmail, member.contactId, member.roles

  • ⚠️ The SDK export is getCurrentMember, NOT getMyMember. The REST method is named Get My Member and the SDK docs page may show GetMyMember, but @wix/members exports it as client.members.getCurrentMember — calling getMyMember(...) throws is not a function at runtime. Silent trap: a logged-out smoke test never reaches the call.

  • ⚠️ Use @wix/members, not the Developer-Preview @wix/site-members.

  • The photo is a wix:image:// identifier — resolve with media.getScaledToFillImageUrl (non-astro.md N7); never hand-build the CDN URL.

⚠️ Do NOT auth.elevate() — wrong axis (and unavailable on a SPA)

Login is the identity axis (anonymous → a specific member). auth.elevate() is the permission axis (→ app/admin scope). A member reading their own data (own profile, own orders/bookings/subscriptions, plan-gated or member-scoped content) is authorized under the member token, no elevation — reaching for elevate to "make member data work" is the wrong axis. A pure SPA has no server, so there is no auth.elevate at all (non-astro.md N5) — and member features don't need it.

Conclusion

Correct custom-login auth:

  • is taken on only when the brief asks for a branded/in-app login form or custom sign-up fields — otherwise the Wix login page (how-to-code-members-{astro,non-astro}.md) is the default;

  • works on any headless project (managed or self-managed) — no project-type branch;

  • reuses the one visitor OAuthStrategy client and drives register / login / processVerification → getMemberTokensForDirectLogin → setTokens, with logout and loggedIn();

  • handles the full loginState machine (SUCCESS / EMAIL_VERIFICATION_REQUIRED / OWNER_APPROVAL_REQUIRED / FAILURE+errorCode), not just SUCCESS;

  • collects custom fields via register's profile — standard fields directly, arbitrary customFields only after defining them (needs the Members Area app);

  • treats signup security (verification / approval / reCAPTCHA) as dashboard-governed, sets none from the run, and states MFA is unsupported headless;

  • persists and renews member tokens like visitor tokens, on one shared client;

  • reads the member via @wix/members getCurrentMember (not the dev-preview package);

  • does no auth.elevate for own-data reads;

  • needs the Wix Members Area app only for profile data and custom-field definitions — pure "logged-in vs not" gating runs on the identity layer with no install.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs Node.js

Security

What our scanner noticed· Low risk

  • Scripts that your agent may run

This skill includes scripts that your agent may run. Read them before you use it.

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Wix
Publisher
Wix (Official)
Source
wix/skills · skills/wix-headless · commit d168bc2
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Wix or Wix.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download wix-headless.zip