Index of every page on this site: llms.txt
All skills
wix avatar

/wix-manage

@e2bc48e official
by Wix.comwix/skills40 stars
42
Run it yourself

REST recipes to configure and manage a Wix site's business solutions — stores, bookings, donations, payments, CMS, and more — and to publish HTML, CSS and JavaScript files as a live Wix site, with or without a Wix account. Open the matching recipe for the exact endpoint, method, and payload before calling — never guess a Wix API, never write Wix dashboard URL from memory. Routes to: automations, stores, bookings, donations, get-paid, CMS, contacts, forms, media, app-installation, custom-apps, pricing-plans, restaurants, ricos rich-content, sites, collaborators, studio-workspace, blog, calendar, domains, events, site-properties, ecommerce, marketing, online-programs, google-ads, google-business-profile, analytics, accessibility, seo, dashboard-navigation.

Use this Skill: https://skilld.dev/gh/wix/skills/wix-manage

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencessitespublish-without-a-wix-account.md

≈1.4k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Publish a Site Without a Wix Account

A shell that reaches https://www.wixapis.com can publish a static site with no Wix login. The site goes live on a *.wix-site-host.com URL and lasts one hour from its creation unless the user claims it; after that every call on it returns 404.

Publish static files: HTML, CSS, JavaScript and assets, up to 20 MiB in all, with an index.html at the top level when there is more than one HTML file. Build a project first and publish its output. A Wix Astro build is released with a login: Upload a Website or HTML Files.

Publish

Generate one UUID as anonymousId and create the site once, not per edit:

# 1. Create: returns { metaSiteId, projectId }
curl -sS -X POST "https://www.wixapis.com/headless-business-setup/v1/headless-business/anonymous/$ANONYMOUS_ID"

# 2. Upload the complete file set: returns { uploadId }; not live yet
curl -sS -X POST \
  "https://www.wixapis.com/headless-business-setup/v1/headless-business/anonymous/$ANONYMOUS_ID/$META_SITE_ID/upload?campaign=api&agent=$AGENT" \
  -F "files=@index.html;filename=index.html" -F "files=@assets/styles.css;filename=assets/styles.css"

# 3. Release: returns { siteUrl }
curl -sS -X POST \
  "https://www.wixapis.com/headless-business-setup/v1/headless-business/anonymous/$ANONYMOUS_ID/$META_SITE_ID/release" \
  -H 'Content-Type: application/json' -d "{\"uploadId\":\"$UPLOAD_ID\"}"

Keep anonymousId, metaSiteId and projectId, and put their values in every later URL, not placeholders. Open siteUrl and check the pages.

$AGENT names what is publishing the site, three parts joined by /: the client product as its vendor writes it, lowercase; the surface, one of chat, work, web, cli, desktop, ide, app; the model as the client's selector shows it. claude-code/cli/opus-5.5, chatgpt/work/gpt-6.1. A part you cannot tell is unknown.

Hand it to the user

Give the live site, {siteUrl}, and the claim link, each on its own line: https://www.wix.com/live-headless-site/{projectId}?anonymousId={anonymousId}. The site lasts one hour unless the user claims it, and then moves to a new address. Whoever opens the link while signed in gets the site; give it only to the user. Never create an account or sign in for them.

Publish changes

# Status: 200 { metaSiteId, projectId, createdAt } while unclaimed
curl -sS "https://www.wixapis.com/headless-business-setup/v1/headless-business/anonymous/$ANONYMOUS_ID/$META_SITE_ID"

# The live files, when you have no copy
curl -sS -o site.zip "https://www.wixapis.com/headless-business-setup/v1/headless-business/anonymous/$ANONYMOUS_ID/$META_SITE_ID/download.zip"
  • 200: upload and release again with the same IDs and every file, changed and unchanged; a release replaces the whole site. Leave the zip's wix.config.json out. The address stays the same.
  • 404: the site was claimed or its hour ended. With the user's login, the HEADLESS site query in Find an existing site finds a claimed site; change it through Change it later. An ended site is gone: say so and ask before creating another.

Claim it

Claiming moves the site into a Wix account and to a new address; the old address stops working. Claim after the last anonymous release, in one of three ways:

  • The claim link: the user opens it in their own browser and signs in or signs up.
  • The Wix MCP (ExecuteWixAPI in your tool list): POST https://www.wixapis.com/headless-business-setup/v1/headless-business/anonymous/{anonymousId}/{metaSiteId}/claim with body {}, through wix.request({ scope: 'account', ... }). The site goes to the account the MCP is signed in as.
  • The Wix CLI: the user approves npx @wix/cli@latest login in their browser; npx @wix/cli@latest token then gives a token that lasts 15 minutes, and the same POST with Authorization: Bearer $ACCESS_TOKEN claims the site into that account.

The claim call returns {}. Read the site's new viewUrl with the HEADLESS site query in Find an existing site and give it with the site's dashboard link, as Verify and report says. Later changes need the user's login: Change it later.

When no shell reaches Wix

The user drags the files onto the drop page in their own browser; the site goes live the same way and the page offers to keep it.

Failures

Failure Action
400 with MISSING_INDEX_HTML, FILE_TOO_LARGE, TOTAL_TOO_LARGE Read details.applicationError.code and fix the files.
404 on any call The site was claimed or its hour ended: see Publish changes.

Offer feedback to Wix when a step fails or guidance is missing.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 alerttoday4 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    The skill is a comprehensive management tool for Wix sites. It contains potential security risks such as an indirect prompt injection surface from site scraping and the ability to define JavaScript-based automation logic, but it includes strong requirements for user confirmation before any site changes.

  • Sockettoday

    No alerts

  • Snyk1d

    Risk: CRITICAL · 3 issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at e2bc48e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 4 days ago
compatibility
Requires Wix REST API access (API key or OAuth).
  • wix
  • rest-api
  • ecommerce
  • bookings
  • cms
  • contacts
  • blog
  • domains
  • restaurants
  • site-configuration
  • api-integration

README badge

README badge for wix/skills/wix-manage

REST API operations for configuring Wix business solutions including stores, bookings, CMS, contacts, domains, and ecommerce. Routes to site setup, entity management (products, services, staff), bulk administrative operations, and server-to-server integrations across Wix's business app ecosystem.

Generated from the current SKILL.md.

Do I need API credentials to use these recipes?
Yes. The skill requires Wix REST API access via either an API key or OAuth token to execute any management operations.
Can I use these recipes to display data on my site frontend?
No. These recipes are for backend REST API operations only — site configuration, entity management, and administrative tasks. They do not cover frontend development or displaying data to users.
What business domains do these recipes cover?
The skill covers stores, bookings, payments, CMS, contacts, forms, media, apps, pricing plans, restaurants, rich content, sites, blogs, calendars, domains, and site properties.
Do these recipes handle OAuth authentication with external services like Google Calendar?
Yes. The external calendar integration recipe covers OAuth-based setup with Google Calendar, Microsoft Outlook, and Apple Calendar for bidirectional event sync.

Generated from the current SKILL.md. These answers refresh after source changes.