ImprovMX API

Name: ImprovMX API
Brand: ImprovMX API
Availability: InStock

✓ Official Vendor SpecCommunicationsEmail Deliverybasic29 EndpointsREST

For Agents

Manage ImprovMX domains, aliases, forwarding rules, SMTP credentials, and email logs programmatically. Useful for support agents and provisioning automation.

Install Jentic One Beta

Connect the ImprovMX API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ImprovMX 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 ImprovMX API.

Add and verify a custom domain for email forwarding

Create, update, and delete email aliases on a domain

Bulk modify aliases in a single call for migrations

Configure SMTP credentials for outbound sending

GET STARTED

Start building with ImprovMX API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use ImprovMX API for, with concrete tasks.

★ Domain and Alias Provisioning

Onboarding flows for new tenants can use the ImprovMX API to add a domain, create the standard set of aliases, and verify that DNS is correctly configured. The /domains and /domains/{domain}/aliases endpoints make this a few API calls rather than dashboard clicks.

Add the domain example.com, create aliases support@ and billing@ both forwarding to ops@example.com, and run the DNS check.

Bulk Alias Migration

When migrating from another forwarding provider, POST /domains/{domain}/aliases/bulk allows aliases to be modified in one batch instead of one call per row. The bulk endpoint reduces migration time and request count for large alias sets.

Bulk update aliases on example.com from a CSV containing 200 rows of alias-to-destination mappings.

Email Log Investigation

Support agents resolving missing-mail tickets can fetch ImprovMX email logs to confirm whether mail arrived, was forwarded, bounced, or was held for spam. Logs include timestamps, source, destination, and outcome to drive a fast triage.

Fetch email logs for domain example.com from the past 24 hours and report any entries with status other than 'forwarded'.

Jentic Email Operations Agent

Through Jentic, an agent can manage ImprovMX domains and aliases from a chat surface. It searches by intent, loads the schema, and executes the right ImprovMX endpoint without context-switching to the dashboard, while Jentic isolates the API key.

Search Jentic for 'create an alias on a domain', load the schema, and create alias help@example.com forwarding to ops@example.com.

Key Endpoints

29 endpoints — improvmx is an email forwarding service that lets you receive mail at a custom domain and route it to any inbox.

METHOD

PATH

DESCRIPTION

GET

/domains

List forwarding domains

POST

/domains

Add a new domain

GET

/domains/{domain}/check

Check domain DNS configuration

POST

/domains/{domain}/aliases

Add an alias to a domain

POST

/domains/{domain}/aliases/bulk

Bulk modify aliases

DELETE

/domains/{domain}/aliases/aliases-all

Delete all aliases on a domain

GET

/domains/{domain}/rules

List forwarding rules

GET

/domains

List forwarding domains

POST

/domains

Add a new domain

GET

/domains/{domain}/check

Check domain DNS configuration

POST

/domains/{domain}/aliases

Add an alias to a domain

POST

/domains/{domain}/aliases/bulk

Bulk modify aliases

Why Jentic?

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

Credential isolation

ImprovMX Basic auth credentials (username 'api' plus API key) are stored encrypted in the Jentic vault. Agents call the API with a scoped Jentic token; the API key never enters the agent's prompt or logs.

Intent-based discovery

Agents search Jentic by intent such as 'create an email alias' or 'check domain DNS' and Jentic returns the matching ImprovMX operations with their input schemas, so the agent does not need to crawl 29 endpoints.

Time to first call

Direct ImprovMX integration: half a day to a day for Basic auth, alias CRUD, and DNS check error handling. Through Jentic: under an hour. Search, load, execute.

FAQs

Specific to using ImprovMX API through Jentic.

What authentication does the ImprovMX API use?

ImprovMX uses HTTP Basic authentication with the username 'api' and your API key as the password. Through Jentic, the credentials are stored in the encrypted vault and the agent receives a scoped Jentic token, so the raw API key never enters the agent context.

Can I bulk update aliases on a domain?

Yes. POST /domains/{domain}/aliases/bulk modifies many aliases in one call, which is the right pattern for migrations and large alias sets. There is also DELETE /domains/{domain}/aliases/aliases-all to clear every alias on a domain at once.

What are the rate limits for the ImprovMX API?

ImprovMX enforces per-account rate limits that depend on plan tier; the OpenAPI spec does not list hard numbers. Bulk endpoints reduce the request count for large mutations, so they should be preferred over per-alias loops.

How do I create an alias through Jentic?

Search Jentic for 'create an alias on a domain' to find the operation backed by POST /domains/{domain}/aliases. Load the schema, pass the domain, alias, and forwarding destination, and execute. Jentic injects the Basic auth credentials at runtime.

How do I confirm DNS is set up correctly for a domain?

Call GET /domains/{domain}/check. The response confirms whether the MX and SPF records are aligned with ImprovMX's expected configuration, which is the fastest way to debug a domain that is not forwarding mail.

Can I retrieve email logs for a domain?

Yes. The Logs endpoints under /domains/{domain} return forwarding events including timestamps, source, destination, and outcome, which support agents use to investigate missing or delayed mail.

ImprovMX API

Connect the ImprovMX API to your agent

Capabilities

Start building with ImprovMX API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs