SMTP
Simple Mail Transfer Protocol (SMTP) is the foundational internet standard for transmitting electronic mail across networks. Defined in RFC 5321 (October 2008), SMTP uses a command-response model over TCP port 25 (or 587 for submission, 465 for SMTPS). It defines commands including EHLO, MAIL FROM, RCPT TO, and DATA, along with a comprehensive set of response codes. SMTP works in conjunction with RFC 5322 (Internet Message Format) which defines the structure of email messages.
SMTP publishes 2 APIs on the APIs.io network. Tagged areas include SMTP, Email, Internet Standards, IETF, and Messaging.
The SMTP catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.
Kin Score
APIs 2
Individual APIs this provider publishes, each with its own machine-readable definition.
RFC 5321 - Simple Mail Transfer Protocol
RFC 5321 is the IETF standard defining the Simple Mail Transfer Protocol. It specifies the client-server protocol used to transmit email across the internet, including the comma...
RFC 5322 - Internet Message Format
RFC 5322 defines the format of electronic mail messages transmitted via SMTP. It specifies the syntax for message headers (From, To, Subject, Date, etc.) and body structure. Wor...
Pricing Plans 1
Published pricing tiers and plan structures.
Smtp Plans Pricing
PLANSRate Limits 1
Documented rate limits and quota policies.
Smtp Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals for API financial operations.
Smtp Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts and semantic vocabularies used across these APIs.
Smtp Context
JSON-LDSpectral Rules 1
Spectral governance rulesets for linting and validating these APIs.
SMTP API Rules
SPECTRALJSON Schema 2
Standalone JSON Schema definitions for this provider's data models.
SMTP Email Message
JSON SCHEMASMTP Session
JSON SCHEMAJSON Structure 1
JSON Structure definitions describing this provider's data shapes.
Smtp Message Structure
JSON STRUCTUREExamples 2
Example request and response payloads for these APIs.
Smtp Message Example
EXAMPLESmtp Session Example
EXAMPLESecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Access & Security 1
Authentication, authorization, and security posture
Other 7
Properties that don't map to a standard resource type
Scroll for all 7
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for providers
9 MCP tools reach this
find_providersBrowse and filter every provider in the catalog.get_provider_artifactsEvery artifact this provider publishes, grouped by type.get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.get_provider_toolsEvery MCP tool they ship, with the operation each wraps.get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.get_provider_ratingPRO — composite, band, trend and facet scores.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/providers/smtp"
curl "https://apis.io/api/v1/providers?limit=25"
curl "https://apis.io/api/v1/providers/smtp/operations?limit=25"
curl "https://apis.io/api/v1/providers/smtp/evidence"
Discovery needs no key. Ratings and market analysis are Pro.