> 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/docs/issuance/flow-1/auto-issuance.md).
# Auto-issuance
The Offer arrives in the Holder's wallet by itself, with nothing to scan and no code to type
A business event fires, the Offer is created, and it reaches the Holder without them asking. An email and a push notification tell them it's there; the Offer waits in **Pending Offers** until they accept. No QR code anywhere in the journey, and no code to type.
This is the lightest journey on the lightest flow, and the right default when issuance is driven by something happening on your side rather than by someone standing at a screen.
### What it requires
* **The Holder uses an EQUS Wallet.** Third-party wallets cannot be delivered into.
* **They are signed in to it as one of your users**, through your identity provider - which is what lets the wallet fetch the `tx_code` on their behalf. See [Bring Your Own IdP](/docs/onboarding/bring-your-own-idp.md).
* **You supply an email address** for the notification. It is used to tell them the Offer is waiting, and is not stored.
If any of these doesn't hold for a given Holder, that Offer can't be auto-issued - send it the ordinary way instead, with the code delivered out of band.
### What the Holder sees
The Offer appears in Pending Offers, the wallet's inbox of Offers waiting to be accepted. Opening the wallet, they see what's on offer and accept it.
Because the Offer waits there, they don't have to act immediately - until it expires, five days after you created it.
### What triggers it
Entirely up to you: a business event, a nightly job, an operator pressing a button in a back office. The distinction isn't how the trigger fires but what happens on the Holder's side - they don't have to be present, or asking, for the credential to reach them.
### Ways to integrate
:code:
Method 1: API
One call from your back end, with autoIssuance and the claim values.
There is no Embed UI method here, and there could not be: Embed UI renders a Holder-facing journey, and this journey has none.
---
# 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/docs/issuance/flow-1/auto-issuance.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.
