Email API
The Email API currently publishes a POST mailbox-management route in the controller catalogue. It is designed for server-to-server workflow integration where mailbox provisioning or related email operations need to be called from another application.
What this API is designed to do
Email API product for mailbox-oriented automation exposed by the active Email controller.
Where it can fit
These are common integration scenarios; the exact use depends on your application, data handling requirements and subscription tier.
Published routes and methods
The endpoint list is read from the existing API controller catalogue. It changes automatically when the catalogue is refreshed.
/email/add_mailboxBody JSON or form:From subscription to first request
Keep access and usage manageable by using the customer dashboard as the control point for keys, whitelist rules and plan limits.
Subscribe to the Email API plan
Create or assign an API key
Whitelist the calling server or domain where appropriate
Send the request body expected by the published endpoint
Review response status and request logs
Before you go live
The active endpoint catalogue is the source of truth for the route and HTTP method. Keep mailbox credentials and administrative data out of client-side code.
Already a customer? Continue from your dashboard.
Sign in to keep purchases, licenses, API keys, downloads, invoices and project requests connected to one account.