Who Has Already Signed

Besides the overall document status, you can find out how individual people are doing — who has already signed or approved, and who is still pending.

Listing signers

curl -H "x-api-key: VAS_API_KLIC" \
  https://api.signi.com/api/v2/contract/ID_DOKUMENTU/signIdentities/list

What you get back — one item per person:

[
    {
        "docs_person": {
            "email": "vas@email.cz",
            "firstname": "…", "lastname": "…",
            "docs_role": "proposer"
        },
        "contract_role": "approve",
        "state": "not approved"
    },
    {
        "docs_person": {
            "email": "protistrana@email.cz",
            "firstname": "Jan", "lastname": "Novák",
            "docs_role": "counterparty"
        },
        "contract_role": "sign_type_a",
        "state": "not signed"
    }
]

Key fields:

• state — the status of the given person: signed / not signed, approved / not approved, stamped / not stamped.
• docs_role — proposer or counterparty.
• contract_role — signing role; the value sign_type_a is the internal designation of the standard sign role.

The reverse view: documents of a given signer

To list all documents in which a specific person is involved:

curl -H "x-api-key: VAS_API_KLIC" \
  "https://api.signi.com/api/v1/contract/list/signer?email_signer=jan@email.cz&state=completed"

{ "contracts": [ { "id": 1234567, "state": "completed", "file_deleted": 0 } ] }

The state parameter is an optional filter (completed / draft / expired / pending).

Where to go next

• Document lifecycle — the overall document status
• Webhooks — completion notifications without polling