skilld
All skills
wix avatar

/wix-manage

@4895cc9 official
by Wix.comwix/skills33 stars
33

REST recipes to configure and manage a Wix site's business solutions — stores, bookings, payments, CMS, and more. 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: stores, bookings, get-paid, CMS, contacts, forms, media, app-installation, pricing-plans, restaurants, ricos rich-content, sites, blog, calendar, domains, events, site-properties, ecommerce, marketing, google-ads, google-business-profile, analytics, accessibility, seo, dashboard-navigation.

Ask your Agent

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

This session only. Nothing lands on disk.

referencesstoresadd-store-pages-to-site.md

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

Add Store Pages to Site

This recipe demonstrates how to add checkout and cart pages to a Wix site when the Stores app is installed but pages are missing.

Overview

When Wix Stores is installed on a site, it should automatically create cart and checkout pages. However, in some cases these pages may be missing. This recipe provides a way to add them programmatically.

Prerequisites

  • Wix Stores app installed on the site
  • API access with site management permissions

Step 1: Add Pages to Site

Endpoint: POST https://www.wix.com/_api/add-pages-to-site/install

Request:

curl -X POST \
  'https://www.wix.com/_api/add-pages-to-site/install' \
  -H 'Authorization: <AUTH>' \
  -H 'Content-Type: application/json' \
  -d '{}'

Response: 200 with {"pagesAdded": ["<widgetId>", ...]} when the call completes within the gateway timeout. On sites with many installed apps the call usually does not complete in time — see the notes below.

If the User Already Got a 504

Answer as troubleshooting, not as a failed install:

What happened What to do Why
504 Gateway Timeout after ~30 seconds Wait 1–2 minutes, then verify that the cart/checkout pages exist and checkout works The gateway timed out while the server-side install may still be running
Pages now exist Do not call the endpoint again The repair completed despite the timeout
Pages are still missing after waiting Call the endpoint once more, then verify again A second call is only warranted after the first run had time to finish

Do not describe an immediate retry as harmless or normally idempotent. The endpoint only adds missing pages, but each call still starts a full scan/add/republish pass, so retrying before the first pass finishes can create overlapping work and another publish.

IMPORTANT NOTES:

  • This endpoint adds missing store pages (cart, checkout) if they don't exist
  • The request body is empty - no parameters needed
  • Only required Authorization header
  • Long-running — a 504 does not mean failure. The endpoint synchronously scans every app installed on the site, adds any missing essential pages, and republishes the site. On real sites this often exceeds the ~30-second gateway timeout, so the call returns 504 Gateway Timeout (sometimes wrapped as Internal Server Error with errorCode: -100) while the installation keeps running server-side and usually completes.
  • On 504, do not retry immediately. An immediate retry starts a second full install-and-republish pass. Wait 1–2 minutes, then verify the missing pages now exist (check the site's store pages, or have the user refresh and re-test checkout). Call the endpoint again only if the pages are still missing.
  • Call it from an HTTP tool that is allowed to reach www.wix.com (for example, the Wix MCP CallWixSiteAPI tool). Sandboxed code-execution tools (such as ExecuteWixAPI) block this host and fail with 403 Forbidden: requests to www.wix.com not allowed.
  • The operation republishes the site. Confirm with the user before running it on a live site.

When to Use This Recipe

Use this recipe when:

  • Checkout flow fails because checkout page is missing
  • Cart functionality doesn't work
  • Store was migrated or had page issues
  • You receive errors about missing store pages

Next Steps

After adding pages:

  • Verify checkout flow works by creating a test order
  • Customize page designs if needed via the Editor
  • Set up payment methods if not already configured

Source: SKILL.md on GitHub

Third-party checks

1 warning1d4 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    The wix-manage skill is an extensive collection of management recipes for Wix sites, covering business solutions such as eCommerce, Bookings, SEO, and site provisioning. It utilizes official Wix REST endpoints and incorporates robust safety patterns, including mandatory user confirmation for sensitive operations and careful validation of site data before mutation.

  • Socket1d

    No alerts

  • Snyk1d

    Risk: MEDIUM · 1 issue

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

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

Last checked against GitHub yesterday.

Activeupdated yesterday

Capability

compatibility
Requires Wix REST API access (API key or OAuth).

Topics

  • wix
  • rest-api
  • ecommerce
  • bookings
  • cms
  • contacts
  • blog
  • domains
  • restaurants
  • site-configuration
  • api-integration

README badge

README badge for wix/skills/wix-manage

What it does

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.

Frequently asked

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.