> For the complete documentation index, see [llms.txt](https://devdocs.joy.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://devdocs.joy.so/joy-javascript-api/joy-loyalty-sdk/js-sdk-tutorial.md).

# JS SDK Tutorial

To help developers build fully custom loyalty interfaces, we maintain an open-source [**Inspiration Hub**](https://github.com/thomasavada/joy-loyalty-custom-sections) containing UI components built with the Joy JS SDK. These examples showcase how to fetch, display, and trigger loyalty data using the SDK — while giving you full freedom to adapt the UI to your own storefront style.

{% embed url="<https://github.com/thomasavada/joy-loyalty-custom-sections>" %}

All example components are available on GitHub and can be used as a starting point for your own implementation. You can clone them, modify the logic, or simply reuse the patterns to speed up development. We know that with AI, we can fine-tune them pretty quickly. Hope that community will contribute more components to that.

{% embed url="<https://screen.studio/share/YCMmxMvJ>" %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://devdocs.joy.so/joy-javascript-api/joy-loyalty-sdk/js-sdk-tutorial.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.