# Oz API

<figure><img src="/files/BTOW2K47EB8nhvHCQI4q" alt=""><figcaption></figcaption></figure>

Oz API is the most important component of the system. It makes sure all other components are connected with each other. Oz API:

* provides the unified Rest API interface to run the Liveness and Biometry analyses,
* processes authorization and user permissions management,
* tracks and records requested orders and analyses to the database (for example, in 6.0, the database size for 100 000 orders with analyses is \~4 GB),
* archives the inbound media files,
* collects telemetry from connected mobile apps,
* provides settings for specific device models,
* generates reports with analyses' results.

For the latest API methods collection, please refer to our [API reference](https://apidoc.ozforensics.com/).

In API 6.0, we introduced two new operation modes: **Instant API** and **single request**.

In the **Instant API** mode – also known as non-persistent – no data is stored at any point. You send a request, receive the result, and can be confident that nothing is saved. This mode is ideal for handling sensitive data and helps ensure GDPR compliance. Additionally, it reduces storage requirements on your side.

**Single request** mode allows you to send all media along with the analysis request in one call and receive the results in the same response. This removes the need for multiple API calls – one is sufficient. However, if needed, you can still use the multi-request mode.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.ozforensics.com/oz-knowledge/guides/developer-guide/api/oz-api.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.