Skip to main content
The terms are in alphabetical order. Each term links to the page that explains it.

API key

A secret token that authenticates requests to the API for one workspace, acting as the user who created it. Production keys start with sajn_svc_ or sajn_usr_, and every sandbox key contains _dev_. See Authentication.

API version

The date-based version of the API and webhook payloads, such as 2026-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 is PENDING_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.

Content

The ordered list of content blocks that a document or template is built from, such as text, an uploaded PDF, a form, or a product table. Each block has a type, a position, and a fieldMeta. Documents and templates return it in content when you pass expand=content. See Content and fields.

Document

One agreement with content, parties, and settings, which moves from DRAFT 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 as document.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

A value in a document’s content that someone fills in: a FORM subfield, a box placed on a PDF, a form field inside a PDF, or an inline <sajn-field> tag in text. See Content and fields.

Field metadata

The fieldMeta object of a content block: its type-specific content and settings. Its type always equals the block’s type. See Content and 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 as customer-name, on a value in a FORM subfield, a placed field, a PDF form field, or an inline field. A key names one field within a document or template. You fill in values by key. See Content and fields.

Organization

The top-level account for your company. It holds billing, members, and workspaces. See Organizations.

Organizer

A party with the role ORGANIZER. Organizers follow the document but don’t sign. See Parties.

Party

A person on a document, with a role, a delivery channel, and a signature method. See Parties.

Placed field

A box on a page of a PDF block, such as a signature mark, a text input, or fixed text. Placed fields are in the PDF block’s fieldMeta.placedFields, with a page counted from 1 and a rect in fractions of the page. See Place fields on a PDF.

Product table

A content block 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 role REVIEWER. 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 role SIGNER. 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 from GET /documents/{id}/parties/{partyId}. See Parties.

Template

A reusable blueprint of fields, parties, and settings. You create documents from it. See Templates and forms.

Webhook endpoint

A URL on your server that sajn sends events to, with the event types it subscribes to, a signing secret, and an API version. See Webhooks.

Workspace

An isolated area of an organization, with its own documents, templates, contacts, members, webhooks, and API keys. See Workspaces.