Mailactor

Limits & capabilities

Discover your effective limits instead of hard-coding assumptions.

GET /v1/me reports your effective organization limits, key restrictions, managed starter usage, and platform caps. Inspect it at the start of an integration and when a policy error occurs.

Managed starter allowance

managedStarter contains limit, used, and remaining. The allowance is lifetime-scoped and shared across your organization's managed inboxes. Deleting messages or creating more inboxes does not reset it.

When exhausted, the API can return configure_customer_domain as the required action. Verified customer-domain inboxes bypass the managed starter allowance but continue to obey normal traffic limits.

Sending and resource limits

organization.sendLimits describes per-minute messages, daily messages, and daily recipients. Domain warm-up and global controls can further restrict sending. Key request-rate limits are distinct from message-send limits.

platformLimits includes recipientsPerMessage, messageContentBytes, inboxes, domains, and webhookEndpoints. Use those deployment values rather than assuming the broad maximum accepted by a schema is your current allowance.

Available now

Create/list/read/delete inboxes; send new messages; read threads; reply to exact messages; export and delete mailbox content; register and verify customer domains; configure signed inbound webhooks; inspect delivery; and passively validate addresses.

Still handled by the team

Organization onboarding, API-key issuance and rotation, permission changes, policy/limit changes, customer-domain removal, and full organization erasure.

Not currently available

A human mailbox UI, public signup, IMAP/POP3, WebSockets, drafts, scheduled sends, arbitrary labels, full-text mailbox search, outbound attachment uploads, or customer-managed attachment scanning. Inbound attachments remain blocked unless their scan state is clean.

On this page