> For the complete documentation index, see [llms.txt](https://support.heyamplify.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.heyamplify.com/bundles-and-upsell/how-to-use-the-javascript-sdk-with-amplify-platform.md).

# How to Use the JavaScript SDK with Amplify Platform

## **What is the JavaScript SDK?**

The **JavaScript SDK** is a browser-based API provided by Amplify that allows developers to access real-time store and bundle information. This SDK enables developers to create custom storefront designs and behavior by integrating advanced logic, event handling, and dynamic interactions.

## **How It Works**

* The JavaScript SDK acts as a bridge between the Amplify Platform and the storefront, providing structured data that developers can use to implement dynamic and customized experiences.
* It is available **only for** [**Amplify One customers**](https://heyamplify.com/pricing/), and merchants must contact the sales team to enable access.
* Developers can use this SDK to modify the way Amplify widgets interact with the store, allowing for advanced styling and custom logic.

## **How to Use the JavaScript SDK**

If you're interested in using the JavaScript SDK:

1. **Ensure you're on the Amplify One plan.** If you are not, [reach out to our sales team ](https://heyamplify.com/?open-demo-popup=true)to discuss upgrading.
2. **Access the API documentation** (not publicly available—[contact our support team](https://support.heyamplify.com/bundles-and-upsell/how-to-contact-support) for details).
3. **Integrate the SDK** in the storefront and modify bundle behavior.

## **Important Notes**

* This SDK is **not a direct customization tool for merchants**—it is meant for developers who wish to integrate dynamic behaviors into their store.
* The resources are constantly expanded to satisfy any scenario. If you have a custom behavior, design, etc. that you want to implement into Amplify bundles, you can [**contact our support team**](https://support.heyamplify.com/bundles-and-upsell/how-to-contact-support) to learn more.

## **Want Access to the JavaScript SDK?**

If you're interested in enabling this feature, please [**contact our sales team**](https://heyamplify.com/?open-demo-popup=true) to learn more about our [**Amplify One plan**](https://heyamplify.com/pricing/) and how it can enhance your store’s customization capabilities. [**Our support team**](https://support.heyamplify.com/bundles-and-upsell/how-to-contact-support) is also available to assist with any questions you might have.


---

# 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://support.heyamplify.com/bundles-and-upsell/how-to-use-the-javascript-sdk-with-amplify-platform.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.
