Developer API

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.

api-email
Published endpoints1
Active plans0
Base daily limit1,000
Base monthly limit30,000
Capabilities

What this API is designed to do

Email API product for mailbox-oriented automation exposed by the active Email controller.

Call the active mailbox endpoint with POST requests
Protect calls with Vismrit API-key controls
Use account-level quotas and whitelist restrictions
Track request activity in the API platform
Use cases

Where it can fit

These are common integration scenarios; the exact use depends on your application, data handling requirements and subscription tier.

Mailbox provisioning workflows
Internal administration automation
Connecting an application to existing email-management operations
Endpoint catalogue

Published routes and methods

The endpoint list is read from the existing API controller catalogue. It changes automatically when the catalogue is refreshed.

MethodRoutePurpose
POST/email/add_mailboxBody JSON or form:
Integration flow

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.

01

Subscribe to the Email API plan

02

Create or assign an API key

03

Whitelist the calling server or domain where appropriate

04

Send the request body expected by the published endpoint

05

Review response status and request logs

Integration notes

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.