Skip to main content

Signers

Signers are individuals who need to interact with a document. Each signer has a unique role and can track their progress through the signing process.

Signer Types

Signers can be either individuals or companies:

INDIVIDUAL

Regular person signing on their own behalf.

COMPANY

Company representative signing on behalf of their organization. Requires company information.

Signer Roles

sajn supports four different signer roles:

SIGNER

The primary role - must sign the document for it to be completed.

ORGANIZER

The person who organized the document. Receives notifications but doesn’t need to sign.

REVIEWER

Reviews the document and can leave comments, but doesn’t need to sign.

ACCEPTOR (deprecated)

Removed. The API still accepts ACCEPTOR on input and silently treats it as SIGNER, so existing integrations keep working, but it is never returned in a response. Use SIGNER instead.

Signer Information

Each signer has the following information:
For company signers:

Required Fields

  • type: Signer type (INDIVIDUAL or COMPANY)
  • name: Signer’s full name
  • Either email OR phone (depending on distribution method)
  • role: Signer role (defaults to SIGNER)
For company signers, also required:
  • companyName: Company name
  • companyOrgNumber: Company organization number

Optional Fields

  • phone: For SMS notifications
  • ssn: Swedish personal number (required for BankID signing)
  • contactId: Link to existing contact in sajn
  • signingOrder: Order for sequential signing

Signing Order

When using sequential signing (signingOrder: "SEQUENTIAL"), assign each signer a number:
The manager must sign first before the employee can access the document. Each signer is notified (email or SMS) only when it becomes their turn — the employee receives no invitation until the manager has signed.
For parallel signing, signingOrder is optional and will be ignored.

Delivery and Signature Settings

Each signer can have individual delivery and signature settings configured when adding them to a document.

deliveryMethod

How the signer receives their signing invitation:

requiredSignature

The signature type required from this signer:
The eID schemes are enabled per account. See Signing Methods for what each one requires.

twoStepVerification

Additional verification before signing: A gate the signer must pass before the document opens. Independent of requiredSignature — you can gate a click-to-sign document behind MitID, for example.
For SMS verification before signing, use twoStepVerification: "SMS_BEFORE_SIGNING" combined with your chosen signature type.
The eID gates are subject to the same per-account availability as the signing methods, and NO_QES is a signing tier only — it is not offered as a gate.

Signer Status

Track each signer’s progress through two status fields:

Read Status

Signing Status

Retrieving Signing URLs

To get a signer’s signing URL, call the get signer endpoint:
Response includes the signing URL:
Each time you retrieve a signing URL, an audit log entry is created. Only fetch signing URLs when you need to share them with signers.
Never share signing URLs publicly. Each URL is tied to a specific signer and should only be sent to that individual.

Linking Contacts

Signers are typically linked to contacts in your sajn account:
This automatically populates signer information from the contact and tracks signing history.

BankID Integration

For BankID signatures, the signer must provide their Swedish personal number (SSN) and have requiredSignature set to BANKID:

Notifications

Signers receive notifications based on their individual deliveryMethod setting:
  • EMAIL: Receives signing invitation via email
  • SMS: Receives signing link via SMS
  • NONE: No automatic notification (retrieve and share the signing URL yourself)
Each signer can have a different delivery method, allowing you to mix email, SMS, and manual distribution in the same document.

Updating Signers

Signers can be updated before they sign:
Once a signer has signed, their information cannot be modified.

Best Practices

Accurate Information

Ensure signer information is accurate before sending - corrections after sending are limited.

Clear Communication

Use the custom message field to provide context about what they’re signing.

Appropriate Roles

Use REVIEWER for people who need visibility but not signing authority.

Sequential for Approval

Use sequential signing for approval workflows where order matters.

Next Steps

Contacts

Learn about managing contacts

Send for Signing

Guide to sending documents