Announcing the MailKite Server developer API: use the client against your own server
MailKite Server now has a developer API that can replace the hosted API for its core send-and-receive path. The practical result is small: point the MailKite client at your server with baseUrl , use an mk_local_… key, and leave application code alone. You can run the backend privately, use MailKite Cloud for outbound delivery, or switch between the two. The deployment target changes. The client…
MailKite Server has announced a new developer API that allows developers to replace the hosted API with their own server. With this API, developers can point the MailKite client at their own server and continue using their existing code. The server can be run privately or use MailKite Cloud for outbound delivery, with the option to switch between the two.
The API is implemented as a Node.js server with a reference backend that uses SQLite as its data storage. It is authenticated using bearer API keys, which are created by the server itself. The API supports sending and inspecting mail, with endpoints for creating and listing messages, as well as retrieving message details. The client libraries have been updated to work with the new API, handling raw non-JSON responses correctly and rejecting unsupported API fields.
The goal of this API is to provide application portability, allowing developers to develop against a private server and deploy without relying on the hosted API. Future updates may include additional features such as domain management, templates, attachment storage, and delivery retry.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
