This section introduces the core concepts required to integrate with the Digital Post Platform.
It explains how the platform is structured, how messages are delivered, and how responsibilities and data flows are organized across organisations, sender identities, and receivers.
Before working with individual APIs, integrators should understand these fundamentals to ensure correct use of the platform and predictable integration behavior.
This introduction section explains the platform concepts you need before integrating and is intended for developers and technical integrators.
It covers:
- The Digital Post Platform in context and roles
- The organisational model and ownership boundaries
- How messages are packaged, delivered, and tracked
- The message lifecycle from submission to delivery
- Core security concepts and controls
- The end to end integration flow
It is a conceptual overview and does not not describe administrative procedures, operational workflows, or user interface behavior.
The Digital Post Platform is a secure infrastructure for large scale digital message delivery between senders and receivers.
The platform is operated by e-Boks and made available to platform holders within defined market setups.
Depending on the market, e-Boks or a partner organization acts as the platform holder, while e-Boks operates the underlying technical platform.
The platform enables:
- Submission of digital messages
- Management of sender identities
- Controlled delivery to receivers
- Secure handling of message content
- Centralized reporting and auditing
All message content is validated, scanned, encrypted, and processed before delivery.
All integrations operate within a structured organisational model.
The platform uses four core concepts consistently across APIs and workflows:
- Platform holder
- Organisation account
- Sender identity
- Receiver
These concepts define ownership, governance, and access boundaries.
Understanding how they relate to each other is required for correct use of sender management, message submission, mailbox access, and reporting APIs.
Detailed explanations are provided in the section Organisational model.
Messages are delivered through structured deliveries that reference message envelopes and content stored in external storage.
Each delivery contains one or more envelopes.
Each envelope defines:
- Sender identity
- Recipients
- Message content
- Message features
- Delivery instructions
The platform guarantees that an envelope is delivered either to all recipients or to none.
Message validation, encryption, and distribution are handled by the platform.
The delivery model is explained in detail in Message delivery model
Each message follows a defined lifecycle from submission to final delivery.
This includes:
- Ingestion and validation
- Recipient identification
- Subscription checks
- Security scanning
- Encryption
- Delivery
- Status reporting
- Optional receipt registration
Understanding this lifecycle is important for handling errors, retries, and reporting.
The full lifecycle is described in Message lifecycle
Message lifecycle section does not contain any information about handling errors and retries. This is covered is covered in Verify and Troubleshoot
The platform applies security controls at multiple levels, including:
- Certificate based authentication
- Token based authorization
- Content encryption
- Access control boundaries
- Audit logging
This documentation describes security mechanisms at a conceptual level only.
Detailed operational security procedures are handled through separate administrative processes.
An overview is available in Security concepts
Most integrations follow the same high level flow:
- Establish organisational and sender context
- Configure system integration and authentication
- Prepare message content and envelopes
- Submit deliveries
- Monitor delivery status and logs
- Retrieve reports and usage data
This flow is described further in Getting Started Overview.
This section is intended to be read before starting technical integration.
It provides the conceptual foundation required for:
- Getting Started guides
- API Reference documentation
- Advanced integration scenarios
After reviewing these pages, integrators should proceed to the Getting Started section to implement their first working integration.