> For the complete documentation index, see [llms.txt](https://doc.ozforensics.com/oz-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.ozforensics.com/oz-knowledge/guides/developer-guide/sdk/sdk-integration-flows-on-premise.md).

# SDK Integration Flows (On-Premise)

Oz SDKs handle media capture on the client side and communicate with Oz API to run liveness and biometric analyses. These guides walk through the end-to-end integration flow for each SDK in an on-premise deployment — from session initialization and capture to submitting the analysis request and retrieving results.

Each guide covers both API modes (Instant and full) and the available integration topologies, so you can see who talks to whom at every step and choose the setup that fits your data-handling requirements. The recommended default for both SDKs is the `capture` topology with Instant API.

Select your SDK to view its flow:

{% content-ref url="/pages/6d647d70fadc1889e15f189ff878e954a48f8821" %}
[Integration Flow Examples for Mobile SDKs](/oz-knowledge/guides/developer-guide/sdk/sdk-integration-flows-on-premise/integration-flow-examples-for-mobile-sdks.md)
{% endcontent-ref %}

{% content-ref url="/pages/2d41cfea73cb94210938bbe477fab86d020beb2c" %}
[Integration Flow Examples for Web SDK](/oz-knowledge/guides/developer-guide/sdk/sdk-integration-flows-on-premise/integration-flow-examples-for-web-sdk.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://doc.ozforensics.com/oz-knowledge/guides/developer-guide/sdk/sdk-integration-flows-on-premise.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.