Amazon Simple Email Service

Name: Amazon Simple Email Service API
Brand: Amazon Simple Email Service
Availability: InStock

★ Only Publicly Available SpecCommunicationsEmail DeliveryapiKey142 EndpointsREST

For Agents

Send transactional and marketing email at scale, manage verified identities, configuration sets, and receipt rules through Amazon SES.

Quickstart

Get started with Amazon Simple Email Service in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"send a transactional email with SES"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Amazon Simple Email Service API.

Send transactional and bulk email from verified domains and email addresses

Verify email identities and domains with DKIM signing for deliverability

Create configuration sets with event publishing for opens, clicks, bounces, and complaints

Manage receipt rule sets that route inbound mail to S3, SNS, Lambda, or WorkMail

GET STARTED

Start building with Amazon Simple Email Service API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for Amazon Simple Email Service, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Amazon Simple Email Service, keeping it validated and agent-ready. Amazon SES is AWS's high-throughput email sending and receiving service for transactional and marketing email. The API covers identity verification, configuration sets, custom verification email templates, dedicated IP pools, receipt rules, sending statistics, and DKIM and bounce handling. It is built for engineering teams that need to send high-volume email from their own domains with deliverability instrumentation rather than depend on third-party email gateways.

Use Cases

Patterns agents use Amazon Simple Email Service API for, with concrete tasks.

★ Transactional Email at Scale

Product teams use Amazon SES to send high-volume transactional emails such as receipts, password resets, and account notifications. The API drives identity verification, template management, and per-message sending so that backend services can move from a third-party gateway to a self-managed sender on their own domain. SES supports up to 14 messages per second on shared infrastructure and substantially higher rates with dedicated IPs after warm-up.

Send a templated email using template OrderConfirmation to customer@example.com from notifications@store.example with a JSON payload containing orderId 12345.

Deliverability Monitoring

Email reliability teams use SES configuration sets and event publishing to track bounce, complaint, and delivery rates per sending domain. The API exposes 15-minute sending statistics windows so that automation can pause sending when bounce rates exceed AWS thresholds, protecting account reputation. This is critical for staying within the 5 percent bounce and 0.1 percent complaint thresholds AWS enforces on shared sending.

Get the send statistics for the last 24 hours and return any 15-minute window where bounce rate exceeded 5 percent.

Inbound Email Processing

Operations teams use SES receipt rule sets to route inbound mail into S3, SNS, or Lambda for parsing and downstream automation. The API manages rule sets, recipient conditions, and action chains so that support inboxes, ticketing intake, and reply-handling systems can be built on top of SES rather than a separate IMAP server. Receipt rules support up to 100 rules per active rule set.

Create a receipt rule in active rule set support-inbound that routes mail addressed to support@example.com into S3 bucket inbound-mail.

Agent-Driven Email Sending via Jentic

AI agents use the SES API through Jentic to send email as part of larger workflows such as customer notifications, alerts, and automated reports. Jentic exposes SES sending operations as discoverable tools so an agent can search by intent, load the schema, and dispatch a message in seconds. This removes the need to embed AWS SDK calls inside every agent code path.

Search Jentic for send transactional email, load the SES SendEmail schema, and execute it with subject Welcome and body Thanks for signing up to user@example.com.

Key Endpoints

142 endpoints — jentic publishes the only available openapi specification for amazon simple email service, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/#Action=CreateConfigurationSet

Create a configuration set

POST

/#Action=CreateReceiptRule

Create a receipt rule

POST

/#Action=CreateReceiptRuleSet

Create a receipt rule set

POST

/#Action=CreateConfigurationSetEventDestination

Add event destinations to a configuration set

POST

/#Action=CreateConfigurationSetTrackingOptions

Configure custom open and click tracking domains

POST

/#Action=CreateCustomVerificationEmailTemplate

Create a custom verification email template

POST

/#Action=CloneReceiptRuleSet

Clone an existing receipt rule set

POST

/#Action=CreateConfigurationSet

Create a configuration set

POST

/#Action=CreateReceiptRule

Create a receipt rule

POST

/#Action=CreateReceiptRuleSet

Create a receipt rule set

POST

/#Action=CreateConfigurationSetEventDestination

Add event destinations to a configuration set

POST

/#Action=CreateConfigurationSetTrackingOptions

Configure custom open and click tracking domains

Why though Jentic?

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

Credential isolation

AWS access keys for SES are stored encrypted in the Jentic vault. Agents receive scoped, short-lived signing access — raw secret access keys never enter the agent context.

Intent-based discovery

Agents search by intent (for example send a transactional email) and Jentic returns matching SES operations with their input schemas, so the agent can call the right action without browsing AWS docs.

Time to first call

Direct SES integration: 1-2 days for SigV4 signing, identity verification flow, and bounce handling. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Amazon Pinpoint Email

Pinpoint Email exposes a similar email-sending surface focused on marketing journeys

Choose Pinpoint Email when the workload is campaign-driven and you want segmentation and journey orchestration alongside sending.

Complementary

Amazon EventBridge

Routes SES delivery, bounce, and complaint events into downstream automation

Choose EventBridge when you need to trigger workflows based on SES sending events without polling sending statistics.

Complementary

AWS Lambda

Processes SES inbound email actions and bounce notifications

Choose Lambda when an SES receipt rule needs to parse or transform inbound mail before storing it.

FAQs

Specific to using Amazon Simple Email Service API through Jentic.

Why is there no official OpenAPI spec for Amazon Simple Email Service?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon Simple Email Service 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 Amazon SES API use?

SES uses AWS Signature Version 4 request signing. Through Jentic, AWS access keys are stored encrypted in the vault and signing happens server-side, so the agent never sees the raw secret access key.

Can I send templated email with this SES API?

Yes. The SendTemplatedEmail and SendBulkTemplatedEmail actions accept a template name and a JSON payload of replacement values. Templates are managed with CreateTemplate and UpdateTemplate actions in the same API.

What are the rate limits for the Amazon SES API?

Sending limits are per-account and start in sandbox at 1 message per second and 200 per day. Production accounts begin at 14 messages per second and scale on request. Bounce rate must stay under 5 percent and complaint rate under 0.1 percent or AWS pauses sending.

How do I verify a sending domain through Jentic?

Search Jentic for verify ses domain, load the schema for the VerifyDomainIdentity action, and execute it with the domain name. Jentic returns the verification token to add as a TXT record at your DNS provider.

Does the SES API include receiving inbound mail?

Yes. Receipt rule sets, receipt rules, and receipt filters in this API control inbound mail routing to S3, SNS, Lambda, and WorkMail. Inbound receiving is region-restricted; check current AWS docs for supported regions.