Signing in an integrated application (API)

The signer doesn't have to wait for an email from Signi — you can trigger the signing directly in your own application. This is handy when the customer needs to sign right away: at a branch, in an e-shop during an order, or in a client portal.

How to do it

1. Create the document via API as usual.
2. In the response, you'll get a signing link for each person in the notifications field:

{
    "contract_id": 1234567,
    "state": "pending",
    "notifications": [
        { "email": "vas@email.cz",
          "links": { "contract": "https://app.signi.com/dashboard/workspace/…/documents/1234567" } },
        { "email": "zakaznik@email.cz",
          "links": { "contract": "https://app.signi.com/signing/…/received" } }
    ]
}

3. Open the link directly in your application — via redirect or in an embedded window. The signer goes through Signi's standard signing wizard.
4. You'll learn about completion via a webhook or by querying the document status.

Emails from Signi are sent as normal — signing can happen either way, whichever comes first.

Signing on a single device

When you're signing with a customer face to face (branch, business meeting), enable this in settings:

"settings": { "one_device": true }

The other party then won't receive their own link (their link in notifications is empty) — they sign together with the proposer on the proposer's device. You can also set this for only selected people — see Signing on a single device.

Where to go next

• Webhooks — automatic notifications of document status changes
• Quickstart — your first document for signing via API