signatureMethod decides how they sign. The methods differ in what they prove: that someone intended to sign, or that a verified person signed. Whichever method you choose, sajn seals the completed PDF with a PAdES seal, so any change to the file after signing is detectable.
Signature levels
The eIDAS regulation defines three levels of electronic signature. Each sajn method maps to one of them:
For most everyday agreements, a simple signature is enough. Use an eID when you need proof of who signed.
Methods
eID schemes are switched on market by market. A
signatureMethod that your account can’t use yet fails with 400 VALIDATION_FAILED, and the issue’s message is This eID scheme is not yet available.
List the available methods
Build a signature-method picker fromGET /helpers/signature-methods instead of a hard-coded list. It returns the methods you can offer, with display labels:
MANUAL, and NONE, which a party gets when its role doesn’t sign. Both are still accepted on input.
Set the method on a party
SetsignatureMethod on each party when you add or update it. Parties on the same document can use different methods:
signatureMethod, the party gets your organization’s default method.
Check who signed
An eID verifies the signer’s identity, but not that it’s the person you intended. To check that, set the party’snationalId, such as a Swedish personnummer. sajn compares it with the identity the eID returns. Without a nationalId, sajn compares names.
To read the identity that each eID verified, call GET /documents/{id}/signatures. It needs the READ_DOCUMENT permission, and for OAuth tokens, the signatures:read scope.
Verify before signing
A signature method controls how the party signs. To check the party’s identity before they sign, set the party’ssignVerification, for example to SE_BANKID or SMS. You can combine the two: a click-to-sign signature behind a BankID check gives you a verified identity with a fast signing step. For the values, see Parties. To check every party before the document opens, set documentMeta.openVerification.
Choose a method
The fastest signing
The fastest signing
Use
CLICK_TO_SIGN. It works in any browser, with no app or credentials.A visible signature on the document
A visible signature on the document
Use
DRAWING. The signer draws a signature, which appears in the signed PDF.Proof of who signed, in Sweden
Proof of who signed, in Sweden
Use
SE_BANKID, and set the party’s nationalId.Proof of who signed, elsewhere in the Nordics or the Netherlands
Proof of who signed, elsewhere in the Nordics or the Netherlands
Use the signer’s national eID:
DK_MITID, FI_FTN, NO_BANKID_BIOMETRIC, or NL_IDIN. For Norwegian agreements that need a qualified signature, use NO_QES.A company signs, in Denmark
A company signs, in Denmark
Use
DK_MITID_ERHVERV. It verifies the company’s identity, with its registration number.Signers in other countries
Signers in other countries
Use
DRAWING or CLICK_TO_SIGN. SE_BANKID works only for people with Swedish BankID.The signer is in the room with you
The signer is in the room with you
Set the party’s
delivery to ["IN_APP"]. The party signs in person on your device.Swedish BankID codes
Swedish BankID isSE_BANKID, both as a signature method and as a verification method. API version 2026-10 rejects the older codes BANKID and BANKID_BEFORE_SIGNING. In API version 2026-09, the API returns BANKID and BANKID_BEFORE_SIGNING, and accepts both spellings on input.
Next steps
Set signing methods
Set the method and verification for each party through the API.
Identity verification
Add a check before the document opens.
Parties
Roles, signing order, delivery, and verification.
Signing certificate
What the signed PDF records about each signature.