> For the complete documentation index, see [llms.txt](https://docs.toolkit.equs.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.toolkit.equs.ai/standards/issuance/flow-2/method-2-api-+-embed-ui.md).

# Method 2: API + Embed UI

A pre-built entry point for starting an authorization-code issuance from your site

{% hint style="warning" %}
**Work in progress.** Embed UI does not yet cover this flow. The page is here so you can plan for it - check with us before building against it.
{% endhint %}

When it lands, Embed UI will provide the website entry point described in [Method 1](/standards/issuance/flow-2/method-1-api.md): the wallet picker and the QR code or deep link that opens a wallet, for a visitor who may not be signed in to your site at all.

The parts that make this flow what it is stay yours either way, because they sit outside the browser:

* Your **Authorization Server**, registered with the platform and handling the wallet's sign-in redirect.
* Your [**Attribute Provider**](/standards/issuance/configuration-attribute-provider.md), called synchronously at signing time.

There is no `tx_code` on this flow, so none of the code-entry or resend machinery that Embed UI provides for the pre-authorized journeys applies here.

### In the meantime

Use [Method 1: API](/standards/issuance/flow-2/method-1-api.md) and your own entry point. If you want a pre-built Holder-facing flow today, [Flow 1](/standards/issuance/flow-1.md) supports Embed UI on both of its user-triggered journeys.


---

# 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.toolkit.equs.ai/standards/issuance/flow-2/method-2-api-+-embed-ui.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.