> For the complete documentation index, see [llms.txt](https://docs.videsk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.videsk.io/es-developers/apps/ejemplos.md).

# Ejemplos

Ejemplos copy/paste para los casos de uso más comunes al construir una app embebida en Videsk.

## Sandbox para QA

Antes de levantar tu propia app, puedes registrar estas URLs sandbox de Videsk como `iframe.url` para validar que tu cuenta, segmento y permisos están bien configurados. Te muestran en pantalla lo que recibe la app, así que sirven para depurar context, scopes y plantillas sin construir nada.

| URL                                                 | Para qué sirve                                                                                                                                                                                                                                                          |
| --------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `https://sdbx.videsk.io/iframes/broker/postmessage` | Verifica el handshake del [broker](https://docs.videsk.io/es-developers/apps/broker.md): muestra el `videsk:init` recibido y el `context` resuelto. Es la versión hospedada del ejemplo [App mínima](https://docs.videsk.io/es-developers/apps/ejemplos/app-minima.md). |
| `https://sdbx.videsk.io/iframes/query-params`       | Muestra los query params resueltos por Handlebars en la URL. Útil para validar [Plantillas y contexto](https://docs.videsk.io/es-developers/apps/plantillas.md) sin un broker.                                                                                          |

{% hint style="info" %}
Cuándo conviene usarlos:

* Validar que tu app aparece en el launcher con la configuración correcta.
* Confirmar que `contextScopes` está entregando los bloques que esperas.
* Probar que tu plantilla Handlebars resuelve los valores correctos.
* Reproducir un bug antes de tocar código de tu lado.
  {% endhint %}

## Ejemplos en código

{% content-ref url="/pages/MNnf2V2HekcPPcvuQYoQ" %}
[App mínima](https://docs.videsk.io/es-developers/apps/ejemplos/app-minima.md)
{% endcontent-ref %}

{% content-ref url="/pages/bF6MH1JaZzBXxYCTmeTa" %}
[Habilitar sesión externa](https://docs.videsk.io/es-developers/apps/ejemplos/sesion-externa.md)
{% endcontent-ref %}

{% content-ref url="/pages/8tCXxlPS8Jrxsyn3pmFh" %}
[Eventos en vivo](https://docs.videsk.io/es-developers/apps/ejemplos/eventos-en-vivo.md)
{% endcontent-ref %}


---

# 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.videsk.io/es-developers/apps/ejemplos.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.
