> For the complete documentation index, see [llms.txt](https://docs-v3.toucantoco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-v3.toucantoco.com/visualizations-and-layouts/embedding/integration/embed-an-app.md).
# Embedding a Toucan App Using iFrames
Although embedding is not a built-in feature for apps, you can integrate a Toucan app within your application using an iFrame. Here’s how:
{% hint style="warning" %}
The Embed SDK is not compatible with iFrames, so SDK functionality will not be available in an embedded Toucan app.
{% endhint %}
## 1. Get Your App URL
Locate the URL of your app in the browser’s address bar. It should look something like this:
```html
https://solution.toucantoco.com/breezy-v3
```
## 2. Create the iFrame
With your app’s URL, you can create an iFrame by using it as the `src` attribute:
{% code overflow="wrap" %}
```html
```
{% endcode %}
## 3. Authenticate the iFrame
To allow user-specific access, you’ll need to pass an authentication token. Follow the steps in the [authentication documentation](/visualizations-and-layouts/embedding/authentication.md) to obtain your token. Then, append the token to the URL using the `embed_token` parameter:
{% code overflow="wrap" %}
```html
```
{% endcode %}
#### Congratulations! 🎉
You’ve successfully embedded a Toucan app within your application!
---
# 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-v3.toucantoco.com/visualizations-and-layouts/embedding/integration/embed-an-app.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.
