> For the complete documentation index, see [llms.txt](https://docs.inji.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inji.io/inji-verify/functional-overview/workflow.md).

# Workflow

### Overview

This section explains how Inji Verify requests and validates verifiable credentials. It covers OpenID4VP-based sharing and QR-based verification.

Use the pages below to understand each verification flow and its implementation details.

* [OpenID4VP Cross Device Flow](/inji-verify/functional-overview/workflow/openid4vp-cross-device-flow.md)\
  The verifier shows a QR code. The wallet scans it and returns `vp_token` via `direct_post`.
* [OpenID4VP Same Device Flow](/inji-verify/functional-overview/workflow/openid4vp-same-device-flow.md)\
  Verifier and wallet run on the same device. The flow uses app redirects.
* [Upload or Scan QR Code flow](/inji-verify/functional-overview/workflow/upload-or-scan-qr-code-flow.md)\
  Verify by scanning or uploading a QR. Supports embedded VC data and OpenID4VP QR codes.
* [Inji Verify SDK](/inji-verify/functional-overview/workflow/inji-verify-sdk.md)\
  UI components and callbacks to embed Inji Verify flows in your relying party app.


---

# 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.inji.io/inji-verify/functional-overview/workflow.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.