Developer Platform
EUnifyer Developer API
Build integrations with EUnifyer — automate org provisioning, sync files, manage calendars and contacts, and receive real-time webhook events.
- REST APIs — Drive, Sites, Partner/MSP, Calendar, Contacts
- Open protocols — CalDAV, CardDAV, IMAP, SMTP, TUS, WOPI
- Outbound webhooks — signed event delivery with retries
- Three auth paths — OAuth 2.0, service accounts, PAT
Base URL
https://api.eunifyer.com/api/v1/API ReferenceScalar Reference · OpenAPI JSON Versionv1 — stable, semantic versioningAuthenticationOAuth 2.0, service accounts, and PAT — choose the right flow for your integration.Partner APIProvision and manage customer organisations programmatically. The MSP and reseller automation surface.Drive APIBrowse, upload, download, share, and delta-sync files.WebhooksReceive signed event notifications for Drive, Sites, Calendar, and org changes.Calendar & ContactsCalDAV and CardDAV protocols plus REST helpers for events and address books.API GuidesError format, pagination, idempotency, concurrency, and rate limits.
Quick start
Pick the auth flow that matches your use case, then call any API endpoint.
| I want to… | Auth flow | Start here |
|---|---|---|
| Build a personal app or CRM plugin acting on behalf of a user | OAuth 2.0 authorization code + PKCE | OAuth quickstart |
| Automate org provisioning or run server-side sync jobs | OAuth 2.0 client credentials (service account) | Service accounts |
| Run a quick script or connect a legacy tool | Personal Access Token (PAT) | PAT quickstart |
What’s available in v1
| Domain | Protocol / API | Status |
|---|---|---|
| Drive (files, folders, shares, delta sync) | REST | GA |
| Sites (pages, workspaces) | REST | GA |
| Partner/MSP (orgs, users, teams, plans) | REST | GA |
| Webhooks (outbound event delivery) | REST + signed HTTP | GA |
| Calendar | CalDAV (primary) + REST | GA |
| Contacts | CardDAV (primary) + REST | GA |
| IMAP / SMTP / JMAP | GA (interop) | |
| User provisioning | REST Partner API | GA |
| SCIM 2.0 provisioning | — | Planned |
What’s not in v1
- Chat content API — deferred due to E2EE complexity (consent and key management).
- Full mail REST API — use IMAP/SMTP/JMAP for now; JMAP external surface being evaluated.
- Bidirectional calendar/contacts REST — CalDAV and CardDAV cover external clients today.
- Graph-style cross-domain API — EUnifyer uses resource-oriented APIs per domain, not a unified Graph.
Common headers
Every authenticated request should include:
Authorization: Bearer <token>
Content-Type: application/jsonResponses include:
| Header | Purpose |
|---|---|
X-Correlation-ID | Trace ID — include in support requests |
X-RateLimit-Limit | Requests allowed per minute |
X-RateLimit-Remaining | Remaining in current window |
X-RateLimit-Reset | Unix timestamp when the window resets |
ETag | Version tag for mutable resources (Sites pages, contacts) |
All requests are org-scoped
Every API call resolves to a single organisation. Your token (PAT, service account, or OAuth token) is always bound to one org. There is no cross-org access; Partner API is the only surface that can manage multiple customer orgs — and that requires a reseller-level credential.
Tools & collections
- Bruno collection — ready-to-run Bruno workspace with the three auth flows plus Partner, Drive, and Webhook requests wired up. Unzip, open in Bruno , select the
ProductionorLocalenvironment, and run01 Auth/Get Service Account Tokenfirst. - Scalar Reference — interactive reference rendered from the public-only OpenAPI schema. Only documents external v1 endpoints — internal admin, auth plumbing, WOPI, and first-party routes are hidden.
- Public OpenAPI JSON — import into Postman/Insomnia or generate clients. Stable contract — matches what partners are allowed to call.