> For the complete documentation index, see [llms.txt](https://docs.xaman.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xaman.dev/concepts/payloads-sign-requests/delivery/deeplink.md).

# Deep Linking

Deep linking in Xumm enables developers to provide a seamless user experience by swiftly guiding users to interact with payloads.

Deep Links are a well known flow to allow users to automatically launch and open another app in a specific state. Xumm allows for a Deep Link workflow, where your application (browser based or native) can trigger Xumm to open and immediately show your sign request.

### Benefits of Deep Linking:

* **When to Use**: Opt for deep linking when you want to minimize user steps and create a fluid transition between your app and Xumm.
* **Device Compatibility**: Deep linking works when the origin (your app or browser) and Xumm are on the same device (iOS/Android).
* **Link Creation**: Generate a deep link that opens Xumm with the payload ready for interaction, making interactions more seamless while keeping users engaged.
* **Return URL**: Set a return URL in the payload to redirect users back to your app or browser post-interaction, maintaining a smooth flow.

### Note for Web Origins:

For web origins, users return to the default browser, not necessarily the original tab. In order to make this smooth, handle session restoration to ensure continuity.

### User Perspective:

For end users, deep linking is a breeze. They tap a link, interact with the payload in Xumm, and return to your app effortlessly.


---

# 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.xaman.dev/concepts/payloads-sign-requests/delivery/deeplink.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.
