> 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.md).

# Developer Guide

In this section, you will find the description of both API and SDK components of Oz Forensics Liveness and face biometric system. API is the backend component of the system, it is needed for all the system modules to interact with each other. SDK is the frontend component that is used to:

1\) take videos or images which are then processed via API,

2\) display results.

We provide two versions of API.

With full version, we provide you with all functionality of Oz API.

{% content-ref url="/pages/-MRahnyAx8txFt-vdWPu" %}
[Oz API](/oz-knowledge/guides/developer-guide/api/oz-api.md)
{% endcontent-ref %}

The Lite version is a simple and lightweight version with only the necessary functions included.

{% content-ref url="/pages/-McUIB8z9JgzTm1Ze3Dn" %}
[Oz API Lite (Deprecated)](/oz-knowledge/guides/developer-guide/api/oz-api-lite.md)
{% endcontent-ref %}

The SDK component consists of web SDK and mobile SDK.

Web SDK is a plugin that you can embed into your website page and the adapter for this plugin.

{% content-ref url="/pages/-MRaiCttauTrCmKj66zU" %}
[Oz Liveness Web SDK](/oz-knowledge/guides/developer-guide/sdk/oz-liveness-websdk.md)
{% endcontent-ref %}

Mobile SDK is SDK for iOS and Android.

{% content-ref url="/pages/-MTSKNnWD\_RUxZQSkdCa" %}
[iOS](/oz-knowledge/guides/developer-guide/sdk/oz-mobile-sdk/ios.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MTSDndKGTvYCXCMuDc9" %}
[Android](/oz-knowledge/guides/developer-guide/sdk/oz-mobile-sdk/android.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.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.