> 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/squarespace.md). # Squarespace Overview of Violet's Squarespace integration for channel developers Squarespace is a website builder and ecommerce platform known for its design-focused templates. Violet integrates via the Squarespace Commerce API. ## Connection Merchants provide a **Commerce API Key** generated in their Squarespace account. This is created under **Settings → Advanced → Developer API Keys**. ## Webhooks Squarespace webhooks are registered automatically after a merchant connects. Violet listens for product and order events. ## Notable Behavior * **Currency objects**: The Squarespace Commerce API represents all monetary values as objects containing a `value` and `currency` code. Violet handles this currency object format natively — no additional configuration is required. * **Discount codes**: Squarespace supports discount codes for Violet-submitted orders. Custom (fixed and percentage) discounts are also supported. * **POS integration**: Squarespace has a point-of-sale (POS) product. Orders submitted through Violet are tagged as online orders and handled through the online order flow. * **Tax**: Squarespace supports both tax-inclusive and tax-exclusive pricing. The interpretation is reflected in the order details returned after submission. * **Inventory**: Squarespace tracks inventory at the variant level. Violet syncs stock quantities from the platform during catalog synchronization. --- # 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/squarespace.md?ask=&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.