# Lookup Object

In order to perform the lookup, uqudo API uses data that is retrieved from the reading step (NFC chip) or, if not available, the optical scanning. The data that come from the NFC chip should be always correct. Data that come from the optical scanning could potentially have OCR errors.

<table><thead><tr><th width="170">Attribute</th><th>Description</th></tr></thead><tbody><tr><td><strong>status</strong></td><td>SUCCESS or FAILED</td></tr><tr><td><strong>statusCode</strong></td><td><p>Available if status is FAILED:</p><ul><li>INVALID_INPUT (e.g. a required field was not properly OCRd)</li><li>ID_NOT_FOUND (ID was not found in the Government database. Could be related to the same problem mentioned for the INVALID_INPUT or because the ID was actually not found)</li><li>UNEXPECTED_ERROR</li><li>SERVICE_UNAVAILABLE (Government database service was not available)</li></ul></td></tr><tr><td><strong>statusMessage</strong></td><td>Status message if any. Can be null</td></tr><tr><td><strong>data</strong></td><td>Available only if status is SUCCESS. See below the details per document type</td></tr></tbody></table>


---

# 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://docs.uqudo.com/docs/kyc/uqudo-sdk/sdk-result/data-structure/lookup-object.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.