Documentation
Connect in three ways.
One os_live_ key works across REST API, SMTP and MCP. Choose the entry point that fits your application.
Three ways to connect
One os_live_ key works across all three entry points.
REST
API
Stable JSON payload, idempotency keys and compatibility endpoints for SendGrid and Resend.
POST https://api.opensender.email/v1/send
Authorization: Bearer os_live_...
SMTP
SMTP
Use WordPress, Laravel, Django, Java or any SMTP client. Same key as API and MCP.
Host: smtp.opensender.email
Port: 587 (STARTTLS) / 465 (TLS)
Username: apikey or os_live_...
Password: os_live_...
MCP
MCP
Connect an AI agent or MCP-compatible client to send and inspect delivery data.
https://api.opensender.email/mcp
Authorization: Bearer os_live_...
Recommended SMTP settings
Username
apikey, password = your os_live_ key. For clients that require a non-empty username, the key itself also works as the username.
SMTP submission vs outbound rDNS
smtp.opensender.email is an authenticated submission bridge: it accepts SMTP, then forwards the message to the REST gateway and your provider. Its own IPv4/IPv6 PTR is not the outbound sending identity. If you operate your own SMTP server, publish a matching PTR for the sending IP, prefer IPv4 when IPv6 rDNS is unavailable, and remove AAAA records rather than sending from an address with no reverse DNS.
REST example
curl -X POST https://api.opensender.email/v1/send \
-H "Authorization: Bearer os_live_..." \
-H "Idempotency-Key: order-1842" \
-H "Content-Type: application/json" \
-d '{"from":"hello@yourdomain.com","to":["customer@example.com"],"subject":"Hello","text":"Sent through OpenSender"}'
MCP configuration
{
"mcpServers": {
"opensender": {
"url": "https://api.opensender.email/mcp",
"headers": { "Authorization": "Bearer os_live_..." }
}
}
}