Connect External Systems

EUnifyer is built on open standards. Any system that supports standard protocols can integrate directly — no proprietary connectors or vendor lock-in required.

This guide covers the most common integration patterns for connecting third-party systems such as education portals, HR platforms, student information systems, and line-of-business applications.

Single Sign-On (SSO)

Protocol: OpenID Connect (OIDC) or SAML 2.0

EUnifyer includes a built-in identity provider. Any application that supports OIDC or SAML can authenticate users through EUnifyer’s SSO.

Setup

In EUnifyer’s admin panel, create a new Client for your external system
Set the client protocol to openid-connect (or saml if your system requires it)
Configure the redirect URI to point to your external system’s callback URL
Copy the Client ID and Client Secret to your external system’s SSO settings

Federation with existing identity providers

If your organisation currently uses Azure AD (Microsoft Entra ID) or Google as an identity provider, EUnifyer can act as an identity broker:

Users sign in with their existing Microsoft or Google credentials
EUnifyer maps them to local accounts
Your external systems authenticate through EUnifyer and get access to both identity sources

This means you do not need to create new credentials for your users. Their existing logins continue to work.

Calendar Integration

Protocol: CalDAV (RFC 4791 / RFC 6764)

EUnifyer exposes a CalDAV endpoint for reading and writing calendar events. Any system that supports CalDAV can sync calendars bidirectionally.

Use cases

Education portals syncing class schedules to teacher/student calendars
Room booking systems checking availability and creating events
HR systems syncing leave and absence to team calendars

Connection details

Setting	Value
CalDAV URL	`https://<your-domain>/api/v1/caldav/`
Authentication	OAuth 2.0 bearer token (from EUnifyer) or Basic Auth
Calendar discovery	`/.well-known/caldav` (RFC 6764)

Contact Integration

Protocol: CardDAV (RFC 6352 / RFC 6764)

EUnifyer exposes a CardDAV endpoint for reading and writing contacts. Any system that supports CardDAV can sync address books.

Use cases

Student information systems syncing student/parent contacts to staff address books
CRM systems keeping contact records in sync
Mobile devices syncing contacts natively (iOS and Android support CardDAV)

Connection details

Setting	Value
CardDAV URL	`https://<your-domain>/api/v1/carddav/`
Authentication	OAuth 2.0 bearer token (from EUnifyer) or Basic Auth
Address book discovery	`/.well-known/carddav` (RFC 6764)

Email Integration

Protocols: IMAP, SMTP, JMAP

EUnifyer’s mail system (powered by Apache James) supports standard email protocols.

Protocol	Port	Use case
IMAP	993 (TLS)	Desktop/mobile email clients, external systems reading mail
SMTP	587 (STARTTLS)	Sending email from external systems (notifications, alerts)
JMAP	HTTPS	Modern API-based email access (faster than IMAP for integrations)

Common integrations

Notification systems sending email via SMTP
Ticketing systems reading incoming mail via IMAP or JMAP
Desktop clients (Outlook, Thunderbird, Apple Mail) via IMAP/SMTP

File Storage Integration

Protocol: S3-compatible API

EUnifyer Drive uses SeaweedFS, which exposes an S3-compatible API. Any system that speaks S3 can read and write files.

Use cases

Document management systems storing files in EUnifyer Drive
Backup tools accessing files via S3
Education portals uploading/downloading assignments and materials

Connection details

Setting	Value
S3 endpoint	`https://<your-domain>/s3/` (or internal SeaweedFS URL)
Authentication	AWS Signature v4 (access key + secret key)
Bucket	Organisation-specific (provided by admin)

Note: For direct user-facing file access, use the EUnifyer Drive REST API instead of S3. The REST API handles permissions, sharing, and versioning.

User Provisioning

Protocol: REST API (SCIM 2.0 planned)

EUnifyer provides a REST API for managing users, teams, and organisations. External systems can use this API to:

Create and deactivate user accounts
Assign users to teams and roles
Query user profiles and group memberships

API authentication

External systems authenticate via OAuth 2.0 (client credentials flow through EUnifyer) or API keys issued by an organisation admin.

SCIM 2.0 (coming soon)

SCIM is the industry standard for automated user provisioning. Once available, systems that support SCIM (most enterprise HR and identity platforms) will be able to automatically sync user accounts with EUnifyer.

REST API

EUnifyer exposes a comprehensive REST API for all modules. External systems can use it for custom integrations that go beyond standard protocols.

Module	Endpoint prefix	Examples
Users	`/api/v1/account/`	Profile, preferences
Calendar	`/api/v1/calendar/`	Events, attendees, reminders
Contacts	`/api/v1/contacts/`	Contact CRUD, groups
Drive	`/api/v1/drive/`	Files, folders, sharing, versions
Mail	`/api/v1/mail/`	Messages, labels, drafts
Chat	`/api/v1/chat/`	Channels, messages, members
Meetings	`/api/v1/meetings/`	Video calls, recordings

Full API documentation is available at https://<your-domain>/api/docs (Swagger/OpenAPI).

Integration Architecture

A typical integration with an education portal or line-of-business system looks like this:


┌─────────────────────┐      OIDC/SAML      ┌──────────────┐
│  Education Portal   │◄────────────────────►│  EUnifyer    │
│  (or any external   │                      │   (SSO)      │
│   application)      │                      └──────────────┘
│                     │                             ▲
│                     │      CalDAV/CardDAV         │ OIDC
│                     │◄──────────────────────┐     │
│                     │                       │     │
│                     │      REST API         ▼     │
│                     │◄─────────────────► EUnifyer API
│                     │                       │
│                     │      IMAP/SMTP        │
│                     │◄──────────────────────┤
│                     │                       │
│                     │      S3               │
│                     │◄──────────────────────┘
└─────────────────────┘

All protocols use the same identity layer. A user who is authenticated in one system is authenticated everywhere.

Frequently Asked Questions

”Our education portal only works with Microsoft 365”

Most systems that claim to “work with M365” are actually using standard protocols underneath — OIDC for login, CalDAV or REST for calendars, IMAP/SMTP for email. Ask the vendor: “Do you support OIDC and CalDAV?” The answer is almost always yes.

If a vendor truly only supports Microsoft Graph API, EUnifyer’s identity brokering still handles the SSO part. For data exchange, EUnifyer’s REST API covers the same functionality as Graph — it just uses a different URL.

”We can’t switch everything at once”

You don’t have to. EUnifyer supports coexistence:

Federate EUnifyer with your existing Azure AD — SSO works for both systems
Run delta imports periodically to keep EUnifyer in sync with M365
Move systems one at a time as you are ready
There is no deadline or big-bang cutover

”What about data we’ve built up over years?”

The import tool handles historical data. We import your full email archive, all calendar history, every contact, and your complete file structure. Nothing is left behind.

”How long does migration take?”

For a typical organisation (100–500 users):

Phase	Duration
Initial setup (credentials, user mapping)	1–2 hours
Data import (runs in background)	4–24 hours depending on volume
Third-party system reconfiguration	1–2 weeks (depends on number of systems)
Coexistence / parallel running	As long as you need

”What if we need help connecting a specific system?”

Contact our integration team. We can provide guidance on connecting your specific education portal, SIS, or other systems to EUnifyer. In many cases it is a configuration change, not custom development.