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.

referencessite-propertieschange-payment-currency-site-properties.md

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

RECIPE: Change a Site's Regional Properties via Site Properties API

Goal

Update a Wix site's regional properties — payment currency, time zone, or primary language — programmatically.

When to use

  • You need to switch a site's store/payment currency (for example, from USD to EUR).
  • You need to change a site's time zone or primary language.
  • You want to automate regional/business setup for sites.

Important notes before you start

  • These fields are part of Site Properties (often shown in the dashboard under regional/business info).
  • A successful update increments the Site Properties version.
  • The update is split into two calls: payment currency and time zone go through Update Business Region (values under businessRegion); primary language goes through a PATCH on the Site Properties root (value under properties).
  • Both calls take a field mask (fields.paths) naming the fields you're updating. Mask paths are top-level field names — see Gotchas.

Step 1 — (Optional) Read current site properties version

This is useful to understand the current snapshot version and other regional fields.

curl -X GET 'https://www.wixapis.com/site-properties/v4/properties' \
  -H 'Authorization: <AUTH>'

Step 2 — Update the properties you need

Payment currency and time zone go through Update Business Region, the documented call for them: put the new values under businessRegion and name each one in a fields.paths mask. Primary language goes through a separate, undocumented call, below — use that call for language only.

Property Field name Value format
Payment currency paymentCurrency 3-letter ISO-4217 code — USD, EUR, GBP
Time zone timeZone IANA time zone name — America/New_York, Europe/Rome
Primary language language 2-letter ISO 639-1 code — en, es, it
curl -X POST 'https://www.wixapis.com/site-properties/v4/properties/business-region' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: <AUTH>' \
  --data-binary '{
    "businessRegion": {
      "paymentCurrency": "EUR",
      "timeZone": "America/New_York"
    },
    "fields": {
      "paths": ["paymentCurrency", "timeZone"]
    }
  }'

A successful call returns an empty object {}.

Primary language: Update Business Region does not accept language. Use PATCH on the Site Properties root. This call has no method reference page, so the request below is its full contract:

curl -X PATCH 'https://www.wixapis.com/site-properties/v4/properties' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: <AUTH>' \
  --data-binary '{
    "properties": {
      "language": "es"
    },
    "fields": {
      "paths": ["language"]
    }
  }'

Expected response

The language call returns only the updated Site Properties snapshot version — it does not echo the properties back:

{ "version": "123" }

To confirm the new value, re-read with the Step 1 GET.

Gotchas & troubleshooting

  • Always send a field mask: omitting fields.paths fails with 400 and "Illegal request - No updates on request body".
  • Mask paths must be top-level fields. The GET response contains a locale object (languageCode, country), which makes a path like locale.timezone look plausible — a nested path is rejected with 400 and "Illegal request - Unknown field in field mask - <path>". Time zone and language are the top-level timeZone and language fields.
  • Currency must be a 3-letter ISO-4217 code (for example, USD, CAD, EUR, GBP).
  • Update Business Region rejects language and locale in its field mask with 400 and "Illegal request - Fields Vector(<fields>) are not allowed for updateBusinessRegion". Set the language with the PATCH call.

Related APIs

  • Site Properties API: REST
  • Get Site Properties (full read shape): REST
  • Stores Currency Converter (conversion utilities, not for setting the site currency):
    • POST https://www.wixapis.com/currency_converter/v1/currencies/amounts/{from}/convert/{to}

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.