Skip to main content
sajn records everything that happens to a document in its activity log: who sent it, who opened it, how each party verified their identity, and when the PDF was sealed. The log is the source of the signing journal and the timestamps on the signing certificate. Activity events aren’t webhook events. Webhooks notify your server about a smaller set of changes as they happen, with dotted lowercase types such as document.party.signed. The activity log is the complete record, which you read when you need it, and its types are uppercase, such as DOCUMENT_SIGNED.

Read the activity log

To read a document’s log, call GET /documents/{id}/activity. It needs the READ_DOCUMENT_AUDIT_LOG workspace permission. The response is a page of events, newest first:
To read the whole log, request the next page with cursor set to nextCursor until hasMore is false. For more information, see Pagination. The response leaves out IP addresses, user agents, and request metadata. Treat type as an open list: sajn can add new types without a new API version.

Delivery

Parties

The party event types keep their original names, from before the API called participants parties.

Document lifecycle

Approval

Document changes

Sealing and timestamps

Swedish BankID

Other eIDs

Verification before opening

Click to sign

Delegation