Tunduk¶

The overview describes the common field interpretation rules, failure reasons, and full/light file formats.

Parent: tunduk_result. Document data retrieved through the Tunduk service, Kyrgyzstan.

Fields of tunduk_result.

Fields marked “Required” are always present within this object. Other fields are included when a value is available; null is excluded from the response.

Field	JSON type	Purpose and conditions
`personal_number`	string	PIN used for the request, up to 14 characters.
`series`	string	Document series.
`number`	string	Document number.
`photo`	string	Retrieved photo: Base64 / a URL in light, when a file is available.
`address`	string	Full address from the provider response, if stored; may be an empty string.
`result_json`	JSON	Other provider data. The nested contract is dynamic.
`result`	boolean	Stored technology result: `true` means accepted, `false` means a negative result. May be absent before calculation; consider the status and the details below.
`failure_reason`	object	Failure reason, if recorded; see the structure.

JSON examples¶

Fragments of the root response object, not complete responses. All values and URLs are illustrative. File formats follow the explanations on this page.

{
  "tunduk_result": {
    "result": true,
    "personal_number": "00000000000000",
    "address": "Example address"
  }
}