Digital Signature¶

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

Digital Signature Identifier¶

Parent: ds_identifier_result. Signer identification for a digital signature; the data provided depends on the identification variant.

Fields of ds_identifier_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
`phone`	string	Signer's phone number.
`iin`	string	Signer's IIN, up to 12 characters.
`bin`	string	Signing organization's BIN, up to 12 characters; may be absent for an individual.
`company_title`	string	Signing organization's name, if applicable.
`is_subject_in_mcdb`	boolean	Whether the user is registered in the Mobile Citizens Database, if checked.
`edocument_response`	JSON	Stored electronic document response for identification. A dynamic structure; light does not transform its contents.
`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.

This block does not return intermediate certificate issuance statuses or certification authority user identifiers.

Digital Signature Signer¶

Parent: ds_signer_result. Document signing outcome.

Fields of ds_signer_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
`document_type`	string, enum	Required: `PDF` — PDF document, `XML` — XML document.
`check_id`	string	Signing check identifier, when available; used to generate signed documents. A separate string identifier, not `session_id`.
`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.

This block does not return a list of signed files, their Base64 contents, or URLs. The signing process status is also absent from both full and light responses.

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.

{
  "ds_identifier_result": {
    "result": true,
    "iin": "000000000000"
  },
  "ds_signer_result": {
    "document_type": "PDF",
    "result": true,
    "check_id": "66666666-6666-4666-8666-666666666666"
  }
}