Automatic Signature by the Proposer (API)

The proposer doesn't have to sign the document manually in the app — by setting autosign_proposers, their signature or approval happens automatically right when the document is created. This is handy when your system generates the documents, the proposer has already seen them, and their manual signature isn't needed. Check with your legal department whether auto-signing is appropriate for your case.

How to do it

Add autosign_proposers to settings:

• for the sign role, the value is the place of signing (e.g. "In Prague") — it will be added to the automatic signature,
• for the approve role, true is enough.

{
    "people": [
        { "is_proposer": true, "email": "vas@email.cz", "contract_role": "sign",
          "positions": [ { "x": 50, "y": 80, "page": 0 } ] }
    ],
    "settings": { "autosign_proposers": "In Prague" },
    "file": "uploaded_file_key"
}

curl -X POST "https://api.signi.com/api/v1/contract/" \
  -H "x-api-key: YOUR_API_KEY" \
  -F "data=@dokument.json;type=application/json" \
  -F "uploaded_file_key=@dokument.pdf"

What happens

In the example above, the proposer is the only signer — so the document signs itself after creation and moves to the completed state (processing takes a moment, the state switches within seconds). If there are counterparties in the document too, the automatic signature applies only to the proposer, and the others receive their invitations as usual. And note: only the first proposer is signed automatically — if there are several, the others must sign manually.

The response at creation looks the same as usual (state: "pending") — you can tell it's finished by querying the document state or via a webhook.

Where to go next

• Document lifecycle
• Document from a template — autosign is useful with templates too