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 Roles

sajn supports four different signer roles:

SIGNER

The primary role - must sign the document for it to be completed.
{
  "role": "SIGNER",
  "name": "John Doe",
  "email": "john@example.com"
}

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

For acceptance-type documents - accepts rather than signs the document.

Signer Information

Each signer has the following information:
{
  "name": "John Doe",
  "email": "john@example.com",
  "phone": "+46701234567",
  "ssn": "197001011234",
  "companyName": "Acme Corp",
  "companyRole": "CEO",
  "companyOrgNumber": "556123-4567",
  "companyId": "company_id_123",
  "role": "SIGNER",
  "signingOrder": 1
}

Required Fields

  • name: Signer’s full name
  • Either email OR phone (depending on distribution method)
  • role: Signer role (defaults to SIGNER)

Optional Fields

  • phone: For SMS notifications
  • ssn: Swedish personal number (required for BankID signing)
  • companyName, companyRole, companyOrgNumber: Company information
  • companyId: Link to existing company in sajn
  • signingOrder: Order for sequential signing

Signing Order

When using sequential signing (signingOrder: "SEQUENTIAL"), assign each signer a number:
{
  "signers": [
    {
      "name": "Manager",
      "email": "manager@company.com",
      "role": "SIGNER",
      "signingOrder": 1
    },
    {
      "name": "Employee",
      "email": "employee@company.com",
      "role": "SIGNER",
      "signingOrder": 2
    }
  ]
}
The manager must sign first before the employee can access the document.
For parallel signing, signingOrder is optional and will be ignored.

Signer Status

Track each signer’s progress through two status fields:

Read Status

StatusDescription
NOT_OPENEDSigner hasn’t opened the document yet
OPENEDSigner opened the document
READSigner read the entire document

Signing Status

StatusDescription
NOT_SIGNEDSigner hasn’t signed yet
SIGNEDSigner has signed the document
REJECTEDSigner rejected the document

Signing URLs and Tokens

Each signer gets a unique, secure URL and token:
{
  "signerId": "signer_123",
  "token": "abc123...",
  "signingUrl": "https://app.sajn.se/sign/doc_123?token=abc123..."
}
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:
{
  "contactId": "contact_123",
  "role": "SIGNER"
}
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):
{
  "name": "John Doe",
  "email": "john@example.com",
  "ssn": "197001011234",
  "role": "SIGNER"
}
When sending the document, specify BankID as the signature type:
{
  "deliveryMethod": "EMAIL",
  "signatureType": "BANKID"
}

Notifications

Signers receive notifications based on the distribution method:
  • EMAIL: Receives signing invitation via email
  • SMS: Receives signing link via SMS
  • NONE: No automatic notification (you handle distribution)

Updating Signers

Signers can be updated before they sign:
PATCH /api/v1/documents/{id}/signers/{signerId}
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

I