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

# Wix

Overview of Violet's Wix integration for channel developers

Wix is a website builder and ecommerce platform used by millions of businesses. Violet integrates via the Wix API using an API key generated in the Wix dashboard.

## Connection

Merchants provide a **Wix API Key** and their **Site ID**. API keys are generated in the Wix dashboard under **Settings → Advanced → API Keys**.

### Required Permissions

The API key must have the following permissions enabled:

| Permission      | Purpose                             |
| --------------- | ----------------------------------- |
| `manage_orders` | Read and update orders              |
| `read_store`    | Access store configuration and info |
| `read_products` | Read product catalog                |

Violet validates all three permissions during the connection attempt by making test API calls to each endpoint. Any permission that returns an authorization error will be reported as a missing scope.

## Webhooks

Webhooks for Wix merchants are registered via the Wix API after a successful connection. Violet receives events for product and order changes.

## Notable Behavior

* **Shipping methods**: Wix does not expose a dedicated API endpoint for retrieving configured shipping methods. Violet assumes shipping methods are configured and proceeds accordingly.
* **OAuth**: The Wix integration currently uses API key authentication rather than a full OAuth flow. Merchants generate keys directly in their dashboard and provide them during onboarding.
* **Site-based access**: Each Wix API key is scoped to a specific site. Merchants with multiple Wix sites will need separate connections for each.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.violet.io/ecom-platforms/wix.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.