> 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/prism/merchants/merchant-app-connections.md).

# Merchant App Connections

For an app to access a merchant’s catalog, the merchant must first connect to the app. Once connected, the channel can browse the merchant’s published products and sell any active offers.

When the connection is established, Violet sends a `MERCHANT_CONNECTED` webhook to the app and a `STORE_CONNECTED` notification to the channel dashboard.

If the merchant later disconnects the app, Violet emits a `MERCHANT_DISCONNECTED` webhook and a `STORE_DISCONNECTED` notification to the channel dashboard. Apps can initiate a disconnect through the [Merchant App Uninstall endpoint](/api-reference/apps/merchant-app-installs/request-merchant-app-uninstall.md).

{% hint style="warning" %}
After disconnection, the app loses all access to the merchant’s catalog and can no longer perform actions. To regain access, the merchant must complete the Violet Connect flow again.
{% endhint %}

Keep in mind that a merchant can be [disabled](/prism/merchants/merchant-enable-disable.md) while still remaining connected to an app.

#### Commission Rate

The commission rate is specific to each merchant–app connection. If that connection is terminated and later re-established, a new rate is applied based on the app’s default commission settings.


---

# 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/prism/merchants/merchant-app-connections.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.