GBDFL¶

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

Parent: gbdfl_result. State Database of Individuals data; a shared block for technology variants.

Fields of gbdfl_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
`iin`	string	Required. IIN used for the request.
`status`	string	Required. Current values: `UNAPPROVED`, `PENDING`, `VALID`, `INVALID`, `TIMEOUT`, `NOT_FOUND`, `FAILED`, `ERROR_ACCEPTED`; see the meanings.
`result_json`	object	Response containing personal data.
`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.

The initial record may contain result: false before data is retrieved. ERROR_ACCEPTED means the scenario is configured to continue on an error, not that a database extract was retrieved.

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.

{
  "gbdfl_result": {
    "iin": "000000000000",
    "status": "PENDING",
    "result": false
  }
}