Last modified: Apr 23, 2026

Attachment

Reference information about the attachment 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.

Attachments represent logical files plus one or more concrete URL representations of those files.

An attachment consists of:

  • metadata such as displayName and optional logical name
  • one or more URLs in urls
  • optional expiresAt

Each URL represents one concrete attachment representation and can vary by:

  • mediaType
  • consumerType

This allows the same logical attachment to be exposed in different formats for different consumers, for example a PDF for GUI frontends and JSON or XML for API consumers.

Attachments can exist at two levels:

  • on the dialog root
  • on individual transmissions

Dialog-level attachments follow dialog-level authorization.

Transmission attachments follow transmission-level authorization. In end-user APIs, transmission attachment URLs are rewritten to urn:dialogporten:unauthorized when the user is not authorized to access the transmission.