> 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/api/oz-api/basic-scenarios/liveness/best-shot.md).

# Best Shot

The "Best shot" algorithm is intended to choose the most high-quality and well-tuned frame with a face from a video record. This algorithm works as a part of the [liveness](/oz-knowledge/guides/developer-guide/api/oz-api/basic-scenarios/liveness.md) analysis, so here, we describe only the best shot part. Starting with API v6.0.1, the best shot is extracted and returned in the API response by default unless disabled for a specific purpose.

{% hint style="info" %}
Please note: historically, some instances are configured to allow Best Shot only for certain gestures.
{% endhint %}

### Processing steps

1\. Initiate the analysis similar to [Liveness](/oz-knowledge/guides/developer-guide/api/oz-api/basic-scenarios/liveness.md#processing-steps), but make sure that `extract_best_shot` is set to `true` as shown below, or this line is omitted (for API 6.0.1 and newer): 

{% code title="request body" %}

```javascript
{
  "analyses": [{
    "type": "quality",
    "source_media": ["1111aaaa-11aa-11aa-11aa-111111aaaaaa"], // // optional; omit to include all media from the folder
    "params" : {
      "extract_best_shot": true // the mandatory part for the best shot analysis
    }
  }]
}
```

{% endcode %}

If you want to use a webhook for response, add it to the payload at this step, as described [here](/oz-knowledge/guides/developer-guide/api/oz-api/use-cases/using-a-webhook-to-get-results.md).

2\. Check and interpret results in the same way as for the pure [Liveness](/oz-knowledge/guides/developer-guide/api/oz-api/basic-scenarios/liveness.md#processing-steps) analysis.

3\. The URL to the best shot is located in the `analyses.results_media -> output_images -> original_url` response under `analyses.results_media -> output_images -> original_name = "ResultImage.jpg"`.


---

# 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/api/oz-api/basic-scenarios/liveness/best-shot.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.