API key
A secret token that authenticates requests to the API for one workspace, acting as the user who created it. Production keys start withsajn_sk_, and sandbox keys with sajn_dev_. See Authentication.
API version
The date-based version of the API and webhook payloads, such as2026-10. You choose it per request with the Sajn-Version header, and the organization has a default. See API versioning.
Approval request
An internal approval of a draft document by workspace members before sajn sends it. While a request is pending, the document’s status isPENDING_APPROVAL. See Documents.
Contact
A reusable record of a person you send documents to. A party created from a contact copies its details. See Contacts.Document
One agreement with content, parties, and settings, which moves fromDRAFT to COMPLETED as it’s sent and signed. See Documents.
eIDAS
The EU regulation on electronic identification and trust services. It defines the simple (SES), advanced (AES), and qualified (QES) signature levels. See Signing methods.Event
A record of something that happened, with a dotted type such asdocument.completed, which sajn delivers to your webhook endpoints. The resource it’s about is in data.object. Every event has an id that stays the same across retries. See Webhook events.
Field
One content block of a document or template, such as text, an uploaded PDF, a form, or a product table. See Fields.Field metadata
ThefieldMeta object of a field: its type-specific content and settings. Its type always equals the field’s type. See Fields.
Form
A public link with questions. Each submission creates a document that the visitor signs. See Templates and forms.Key
A stable name, such ascustomer-name, on a value in a FORM subfield, a placed field, or a PDF form field. You fill in values by key. See Fields.
Organization
The top-level account for your company. It holds billing, members, and workspaces. See Organizations.Organizer
A party with the roleORGANIZER. Organizers follow the document but don’t sign. See Parties.
Party
A person on a document, with a role, a delivery method, and a signature method. See Parties.Placed field
A box on a page of a PDF field, such as a signature mark, a text input, or fixed text. Placed fields are in the PDF field’sfieldMeta.placedFields. See PDF field placement.
Product table
A field that lists products or services with prices, quantities, discounts, and totals. A party can choose rows and quantities. See Product tables.Reviewer
A party with the roleREVIEWER. Reviewers are invited to review the document but don’t sign. See Parties.
sajn ID
An identity check with Swedish BankID that isn’t tied to a document. The API calls it an identity check, at/identity-checks. See sajn ID.
Sandbox
A separate, linked organization for testing. Nothing is billed, BankID is mocked, and signed PDFs are watermarked. See Sandbox.Seal
The PAdES electronic seal that sajn applies to every completed PDF, so any later change to the file is detectable. See Signing certificate.Signer
A party with the roleSIGNER. A document completes when every signer has signed. See Parties.
Signing certificate
The page that sajn appends to every completed PDF. It records who signed, how they verified their identity, and when. See Signing certificate.Signing order
Whether parties sign at the same time (PARALLEL) or one after another (SEQUENTIAL), set in documentMeta.signingMode. In SEQUENTIAL mode, each party’s signingOrder sets its position. See Parties.
Signing URL
The personal link a party opens to sign. Get it fromGET /documents/{id}/parties/{partyId}. See Parties.