> For the complete documentation index, see [llms.txt](https://docs.intents.aurora.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intents.aurora.dev/intents-swap/widget-integration.md).

# Widget integration

You can embed ready-to-be used **Swap Widget** directly into your app using an **iframe** or a **React component**.

{% stepper %}
{% step %}

### Create Intents Studio account

Navigate to [Widget Studio](https://studio.aurora.dev/) and log in with your email using the button in the top-right corner of the interface.
{% endstep %}

{% step %}

### Configure the widget

Make sure to use **Swap** Widget mode.

In the UI, you can configure settings such as the displayed Networks and Tokens, and how the Wallet Connection is handled.
{% endstep %}

{% step %}

### Configure the design

You can also customise the design to match your branding with different Styles, Accents, or Layouts. Reach out to our team for more advanced styling options.
{% endstep %}

{% step %}

### Embed the widget

Click the **Embed in your app** button on the top right of the interface, either through:

* An iframe by using **Generate a new link to embed** section
* Or React component using **Use React code snippet**
  {% endstep %}

{% step %}

### (Optional) Use advanced settings of the widget

If you decide to embed a React component, you can use advanced settings, such as your own wallet connection or use widget hooks. Check the detailed docs on the [Widget Configuration](/intents-swap/widget-configuration.md).
{% endstep %}
{% endstepper %}


---

# 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.intents.aurora.dev/intents-swap/widget-integration.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.