Mailu API

Name: Mailu API
Brand: Mailu API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsEmail DeliveryapiKey25 EndpointsREST

For Agents

Provision and manage a self-hosted Mailu mail server: create users, aliases, and domains, configure relays, and set up fetchers. Used by agents that automate hosting setup for self-managed email.

Install Jentic One Beta

Connect the Mailu API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Mailu API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Mailu API.

Create a new mailbox user under a managed domain with quota and password

Add or remove a forwarding alias that points to one or more destinations

GET STARTED

Start building with Mailu API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Mailu API for, with concrete tasks.

★ Automated User Provisioning

Self-hosted Mailu deployments often back small companies and homelabs that add and remove users frequently. The user endpoints create, update, and delete mailboxes under a managed domain with quota, password, and forward settings, so an HR or onboarding script can provision a new starter's mailbox in seconds. The same flow handles offboarding by deleting or disabling the user.

POST /users with email new.starter@company.com, password, and quota — then verify with GET /users/{email}.

Alias and Forwarding Management

Group addresses, role mailboxes, and personal forwarding rules are managed as Mailu aliases. The alias endpoints create, update, and delete forwarding rules that point a single address at one or more destinations. Operators can rotate role mailbox owners or disable a leaked address without touching the underlying user.

POST /aliases creating sales@example.com pointing at [alice@example.com, bob@example.com] with copy-on-keep enabled.

Domain and Relay Configuration

Adding a new domain to a self-hosted Mailu instance is a multi-step task: create the domain in admin, configure MX in DNS, optionally set up relay rules. The Mailu domain endpoints handle the admin side and the relay endpoints register upstream forwarders for outbound traffic. Together they let an automation script bring a new domain online without console access.

POST /domains with name 'newcompany.io', then POST /relays for upstream-relay.example.com to handle outbound.

AI Agent Postmaster Assistant

Operators of self-hosted mail servers benefit from agents that triage common admin requests: 'add a forwarder', 'reset a password', 'delete a stale alias'. Through Jentic the agent searches by intent, loads the schema, and executes the right Mailu admin call. The API token stays in the vault rather than in the agent's context.

Use Jentic to search 'add forwarding alias on mailu', execute POST /aliases with the requested forward, and confirm by listing the alias back.

Key Endpoints

25 endpoints — jentic publishes the only available openapi specification for mailu api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/users

Create a user

GET

/users/{email}

Get user details

POST

/aliases

Create an alias

POST

/domains

Create a domain

POST

/relays

Create a relay domain

POST

/fetch

Create a fetcher

POST

/users

Create a user

GET

/users/{email}

Get user details

POST

/aliases

Create an alias

POST

/domains

Create a domain

POST

/relays

Create a relay domain

POST

/fetch

Create a fetcher

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Mailu API token is stored encrypted in the Jentic vault. Agents call the API through a scoped execution token and Jentic injects the Authorization header server-side, so secrets never enter agent context.

Intent-based discovery

Agents search by intent (e.g., 'create a mailu user') and Jentic returns the matching admin endpoint with its input schema — no need to keep the 25-operation surface in the agent's prompt.

Time to first call

Direct Mailu integration: a couple of hours per workflow, plus the operator effort of locating the admin token. Through Jentic: under 30 minutes — search, load, execute.

FAQs

Specific to using Mailu API through Jentic.

Why is there no official OpenAPI spec for Mailu API?

Mailu does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Mailu API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Mailu API use?

Mailu uses an API token passed in the Authorization header, configured in the admin interface of the self-hosted instance. Through Jentic the token is encrypted in the vault and injected at execute time, so it never enters the agent context.

Can I create a new mailbox user through the API?

Yes. POST /users with email, password, and quota creates the mailbox. GET /users/{email} returns the configured user, and PATCH or DELETE update or remove it.

How do I forward mail from one address to another on Mailu?

Create an alias with POST /aliases where the source is the public address and destination is the list of recipients. Update the alias with PATCH /aliases/{email} or remove it with DELETE.

What are the rate limits for the Mailu API?

Mailu is self-hosted, so rate limits depend on the operator's deployment rather than a managed quota. The OpenAPI spec does not declare limits — keep request rates reasonable to avoid pressure on the admin process.

How do I provision a Mailu user through Jentic?

Run pip install jentic, search 'create mailu user', load the schema for POST /users, and execute with email, password, and quota. Jentic injects the API token from the vault at request time.

Mailu API

Connect the Mailu API to your agent

Capabilities

Start building with Mailu API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs