The signer can sign with a qualified certificate stored remotely at I.CA (the RemoteSign service) — the certificate is not on a card or in the computer, and the signer confirms the signature in their I.CA RemoteSign app. You just need to assign them the sign_remote_sign role.
The signer must have I.CA RemoteSign linked to their Signi account — see Remote Sign. The method must be enabled in the workspace; see Signing roles.
Example
{
"people": [
{ "is_proposer": true, "email": "vas@email.cz", "contract_role": "approve" },
{ "is_proposer": false, "email": "protistrana@email.cz", "contract_role": "sign_remote_sign",
"first_name": "Jan", "last_name": "Novák", "person_type": "nature",
"positions": [ { "x": 50, "y": 80, "page": 0 } ] }
],
"file": "uploaded_file_key"
}
curl -X POST "https://api.signi.com/api/v1/contract/" \
-H "x-api-key: VAS_API_KLIC" \
-F "data=@dokument.json;type=application/json" \
-F "uploaded_file_key=@dokument.pdf"
The response is the same as for a standard creation (contract_id, notifications with links). The difference is on the signer's side — in the signing wizard they confirm the signature via I.CA RemoteSign.
Where to go next
- Setting up I.CA RemoteSign in Signi
- Signing with a certificate and Signing via Bank iD — other higher-level signing methods
- Signing roles — who does what with a document
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article