Seen

Reference information about the seen log entity

Select environment: Help

This dropdown lets you select which Dialogporten environment the content of this page should be based on. If unsure, use the default "Staging (TT02)", as this is the environment you would normally test against when integrating Dialogporten.

For bleeding edge, select "Dev", as this contains the most recent unreleased changes to the Dialogporten API. Select "Local dev" if you want to test changes to Dialogporten itself running locally.

The schema below shows the seen-log entity returned in dialog details.

Seen-log entries are created automatically when a dialog details endpoint is used to retrieve a dialog. Search/list operations do not create seen-log entries.

The implementation stores seen information per user and per dialog revision:

if the same user reads the same dialog revision multiple times, only the first access is recorded
when the dialog changes and a new revision is created, a new seen-log entry can be created for the same user

Each entry contains:

id
seenAt
seenBy
isViaServiceOwner, which identifies entries created through a service-owner-operated frontend
isCurrentEndUser

Seen-log data is also used when calculating isContentSeen. A dialog is only considered content-seen if it has been retrieved since its last content update and it does not have the system label MarkedAsUnopened.