Developers

Everything in Mailocity and Zappocity has an API: the same ones the web apps use. The documentation below comes from the specs the server is tested against, so it is always current.

Mailocity

Mailocity admin API 1.25.0

Platforms, team owners and admins: tenants, domains, users, filters, archive and support (/v1).

Mailocity webmail API 1.19.0

Webmail's own endpoints next to JMAP: sign-in, settings, security, sharing and mail app settings (/api/mail).

Mailocity signup API 1.3.1

Public sign-up and invitations (/api/signup).

Zappocity

Zappocity account API 1.6.0

Zappocity accounts: sign-in, organizations, billing and support requests (/api/account).

Zappocity platform API 1.9.0

Zappocity's platform for staff and products: products, subscriptions, billing, payments and the help desk (/v1/platform).

Standard protocols

JMAP

Mail, submission, contacts, calendars, Sieve, quotas, blobs, sharing and push (RFC 8620, 8621 and the rest) at /.well-known/jmap, over HTTP and WebSocket.

CalDAV and CardDAV

Calendars and contacts for Apple, Thunderbird, DAVx⁵ and others, at /.well-known/caldav and /.well-known/carddav.

IMAP and SMTP

IMAP4rev2 on 993 and SMTP submission on 587, with ManageSieve on 4190 for filters.

Signing in

The admin API takes a platform key or a team API key (Authorization: Bearer); team keys reach their own team only. Webmail and account endpoints use the browser session with an X-CSRF-Token header. Mail apps and scripts use the account's password, an app password, or a mailbox token (cs_mt_) for JMAP and sending.