How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Mailgun website screenshot

Mailgun

Mailgun (by Sinch) is a transactional email API service for developers to send, receive, validate, and track emails at scale. The platform provides SMTP and HTTP APIs for sending email, inbound message routing, deliverability analytics, suppression management, and email validation with regional endpoints for US and EU data residency.

agent aware

Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.

Kin Score

API Evangelist profiles Mailgun the way a machine reads it — 23 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Mailgun scores 33.0/100 (thin), with a separate agent-readiness read of 17/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Mailgun Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Mailgun's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/mailgun/"
   title="Mailgun on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/mailgun.svg"
       alt="Mailgun Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Mailgun

Each block below is one kind of artifact we hold for Mailgun. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 8

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

Mailgun Email Validation API

REST API for verifying email addresses in real time, bulk list validation, and deliverability scoring to reduce bounces and improve sender reputation.

Mailgun Domains API

The Domains API from Mailgun — 2 operation(s) for domains.

Mailgun Events API

The Events API from Mailgun — 1 operation(s) for events.

Mailgun Mailing Lists API

The Mailing Lists API from Mailgun — 1 operation(s) for mailing lists.

Mailgun Messages API

The Messages API from Mailgun — 2 operation(s) for messages.

Mailgun Routes API

The Routes API from Mailgun — 1 operation(s) for routes.

Mailgun Suppressions API

The Suppressions API from Mailgun — 3 operation(s) for suppressions.

Mailgun Webhooks API

The Webhooks API from Mailgun — 2 operation(s) for webhooks.

Scroll within the panel for all 8 ·

Open Collections 10

Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Mailgun Domains API

OPEN COLLECTION

Mailgun Webhooks

OPEN COLLECTION

Mailgun API

OPEN COLLECTION

Scroll within the panel for all 10 ·

GraphQL 1

Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.

GraphQL schemas published by this provider.

Mailgun GraphQL

Mailgun is a REST-only email delivery API platform. No native GraphQL endpoint is publicly offered. This document describes a conceptual GraphQL layer derived from Mailgun's RES...

GRAPHQL

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Mailgun Authentication

http · 1 scheme

SECURITY

Mailgun Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Mailgun Trust Center

SOC 2, ISO 27001, PCI DSS, HIPAA, GDPR

SECURITY

Agentic Access 1

An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.

Recommended x-agentic-access execution contracts for AI agents.

Mailgun Agentic Access

17 operations · 8 acting

17 operations · 8 acting

AGENTIC

Resources

Every other property we hold for Mailgun — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Get Started 2

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Commercial 1

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/mailgun · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of Mailgun, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.