Values filled in a template (API)

ℹ️ New — available from the beginning of November 2026.

When a document from a template has fields that are filled in by the counterparty, you get the filled values back through the API — you don't have to extract them from the signed PDF.

How to do it

After being sent, a document with counterparty fields is in the waiting_for_answers state — the counterparty first fills in the fields, then signs. You can read the values at any time:

curl -H "x-api-key: VAS_API_KLIC" \
  https://api.signi.com/api/v1/contract/1234567/fields

Response (verified example — a template with a single counterparty field):

{
    "fields": [
        {
            "id": "122",
            "name": "Připomínky",
            "value": "Testovací připomínka vyplněná protistranou",
            "filled_by": "counterparty",
            "filled_by_email": "protistrana@email.cz",
            "filled_by_docs_person_id": 1234503,
            "assigned_to": { "role": "counterparty", "party_order": null }
        }
    ]
}

Key fields:

• value — the filled value; null until someone fills the field in.
• filled_by / filled_by_email / filled_by_docs_person_id — who filled in the value (proposer / counterparty).
• assigned_to — who the field is intended for (role, and for multi-party templates party_order).

The values are available immediately after being filled in — you don't have to wait for signing or for the document to be completed. You'll find out that filling in is finished when the document moves out of the waiting_for_answers state (see Document lifecycle), and about signatures via a webhook.

The same endpoint also returns fields of a form document from a PDF with tags.

Where to go next

• Document from a template — how to create a document from a template
• Filling in details into a template by the counterparty — how the counterparty sees it
• Form document from a PDF with tags