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.

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

This session only. Nothing lands on disk.

referencessitesread-site-context.md

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

Read Account or Site Context

Returns a site's name, URL, status, locale/region, and all installed apps with human-readable display names.


Markdown endpoint (recommended)

Endpoint: POST https://www.wixapis.com/_api/dynamic-context/v1/dynamic-context/markdown

Returns { "markdown": "..." }.

Account token + siteId — one specific site

curl -X POST \
  'https://www.wixapis.com/_api/dynamic-context/v1/dynamic-context/markdown' \
  -H 'Authorization: <AUTH>' \
  -H 'Content-Type: application/json' \
  -d '{"siteId": "<metaSiteId>"}'

Response:

## 1. Acme Store

**ID**: `<metaSiteId>`
**URL**: [https://example.wixsite.com/acme](https://example.wixsite.com/acme)
**Status**: Published
**Editor Type**: Editorless
**Created**: Aug 14, 2026, 05:21 · **Updated**: Aug 17, 2026, 20:44
**Velo**: Enabled

### Properties

**Locale & Region**
- Language: **en**
- Country: **US**
- Timezone: **America/New_York**
- Currency: **USD**

### Apps

- **Wix Stores** (ID: `215238eb-22a5-4c36-9e7b-e7c08025e04e`) — Catalog app version: **V3**
- **Wix Bookings** (ID: `13d21c63-b5ec-5912-8397-c3a5ddb27a97`)
- **Wix Blog** (ID: `14bcded7-0066-7c35-14d7-466cb3f09103`)

Without siteId

curl -X POST \
  'https://www.wixapis.com/_api/dynamic-context/v1/dynamic-context/markdown' \
  -H 'Authorization: <AUTH>' \
  -H 'Content-Type: application/json' \
  -d '{}'
  • Account token: returns up to 10 sites. If the account has more: _Showing 10 sites (more available)_ — call again with a specific siteId.
  • Site-scoped token (e.g. the Wix connector in Base44): returns the one site the token is scoped to.

JSON endpoint

Endpoint: POST https://www.wixapis.com/_api/dynamic-context/v1/dynamic-context

Same request shape. installedApps contains raw appId UUIDs — extract only what you need:

const res = await fetch(
  "https://www.wixapis.com/_api/dynamic-context/v1/dynamic-context",
  {
    method: "POST",
    headers: { Authorization: `Bearer ${accessToken}`, "Content-Type": "application/json" },
    body: JSON.stringify({ siteId: metaSiteId }),
  }
);
const { sites } = await res.json();
const site = sites[0];

const KNOWN_APPS = {
  stores:       "215238eb-22a5-4c36-9e7b-e7c08025e04e",
  bookings:     "13d21c63-b5ec-5912-8397-c3a5ddb27a97",
  blog:         "14bcded7-0066-7c35-14d7-466cb3f09103",
  events:       "140603ad-af8d-84a5-2c80-a0f60cb47351",
  pricingPlans: "1522827f-c56c-a5c9-2ac9-00f9e6ae12d3",
  restaurants:  "13e8d036-5516-6f75-e025-2aca3b5d7930",
};

const appById = Object.fromEntries(
  (site.installedApps ?? []).map((a) => [a.appId, a])
);

const context = {
  id:              site.id,
  name:            site.displayName,
  url:             site.url,
  currency:        site.properties?.paymentCurrency,
  locale:          `${site.properties?.locale?.languageCode}-${site.properties?.locale?.country}`,
  timezone:        site.properties?.timeZone,
  hasStores:       !!appById[KNOWN_APPS.stores],
  storesCatalogV:  appById[KNOWN_APPS.stores]?.catalogVersion ?? null, // "V3" | "V1" | null
  hasBookings:     !!appById[KNOWN_APPS.bookings],
  hasBlog:         !!appById[KNOWN_APPS.blog],
  hasEvents:       !!appById[KNOWN_APPS.events],
  hasPricingPlans: !!appById[KNOWN_APPS.pricingPlans],
  hasRestaurants:  !!appById[KNOWN_APPS.restaurants],
};

API Reference

Source: SKILL.md on GitHub

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

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
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.