Delegating a signature (API)

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

Delegating a signature — transferring the ability to sign to another person — is also possible via the API, to the same extent and under the same rules as in the app.

How to do it

First, find the docs_person_id of the signer from the document detail:

curl -H "x-api-key: YOUR_API_KEY" \
  "https://api.signi.com/api/v1/contract/1234567?with=people"

{ "people": [ { "docs_person_id": 1234503, "email": "counterparty@email.com", "is_proposer": false } ] }

Then delegate the signature to another person:

curl -X PUT "https://api.signi.com/api/v1/contract/1234567/docsPerson/replace/1234503" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "docs_person": {
      "email": "new.signer@email.com",
      "first_name": "Petra",
      "last_name": "Svobodová",
      "identity_form": "nature",
      "docs_role": "counterparty",
      "mobile": "+420601000000"
    },
    "signature_footer": "Petra Svobodová, on behalf of"
  }'

{ "docs_person_id": 1234503 }

The same docs_person_id is returned — the slot on the document keeps its identifier, only the person on it changes.

The new person receives a request to sign, and the original link stops working.

Rules

• docs_role is required — counterparty or proposer depending on the delegated party.
• You can only delegate a party that has not yet signed.
• Only if the document and workspace allow it — otherwise it returns 400.
• For a corporate party, you can also send organization_name, organization_position, organization_ico, and other company details.

Where to go next

• Delegating signatures — how it works in the app
• Delegating signatures from the counterparty's perspective
• Who has already signed — the status of individual signers