> For the complete documentation index, see [llms.txt](https://docs.kula.digital/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kula.digital/your-data-sources/wix.md).

# Wix

Wix brings your **bookings, members, pricing plans, and online-store orders** into Kula Intelligence.

## What we read — and what we don't

* **We read:** contacts and members, bookings and attendance, pricing plans, online-store orders and products, your staff and locations, and basic business info — read-only.
* **We don't:** change your site, your bookings, your plans, or your store.

## What you'll need

* A **Wix API key** with read access to Contacts, Bookings, Pricing Plans, eCommerce, and Business Info (created in the Wix **API Keys Manager**).
* Your **Site ID** (from your Wix dashboard URL).
* Your **Account ID** is optional and only needed for some setups.

## How to connect

1. In the **Wix API Keys Manager**, create a key with *read* access to the areas listed above.
2. In Kula, open **Connectors → Wix**, paste the key and your Site ID, and click **Test**. A failure here means the key or Site ID is wrong — not a broken setup.
3. Click **Connect**, then run the **import** to land your history.
4. When the import finishes, click **Process** to turn it into the tidy members, sales, and attendance the AI reads. A big store can take around 20 minutes to process — it runs in the background.

## Good to know

* Wix exposes different kinds of data through different parts of its API, and they don't all behave the same way. Kula handles each, but if a particular kind of data ever looks unexpectedly thin, let us know so we can check it.
* Re-running the import only fills gaps; **Process** is safe to click again.

## If it stops working

Usually the API key was rotated or its access narrowed. Generate a fresh key with the right read access and re-enter it. See [Keeping your connectors healthy](/your-data-sources/operating.md).