canonical: https://jentic.com/apis/amazonaws.com/amazon-ses # AWS Amazon Simple Email Service 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. ## For AI agents Send transactional and marketing email at scale, manage verified identities, configuration sets, and receipt rules through Amazon SES. ## Scope Does not handle SMS, push notifications, voice messages, or campaign segmentation - use for email sending and receiving via SES only. ## Capabilities - 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 - Operate dedicated IP pools and warm-up policies for high-volume senders - Create and send custom verification emails to confirm new sender addresses - Read sending statistics including delivery, bounce, and complaint rates per 15-minute window ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **Identities** — Verify and manage sending domains and email addresses - **Configuration Sets** — Group sending behaviour with event destinations and tracking options - **Receipt Rule Sets** — Define rules for processing inbound mail - **Templates** — Manage reusable email templates with variable substitution - **Dedicated IPs** — Manage dedicated IP addresses and warm-up policies ## Why Jentic - **Setup:** Wiring Amazon Simple Email Service by hand means building SigV4 request signing, resolving the regional email.{region}.amazonaws.com host, and handling the query-style Action dispatch plus AWS retries yourself. Through Jentic you install once, import Simple Email Service from the API Directory, store the AWS access keys once, and your agent calls it. - **Permission scoping:** Simple Email Service dispatches every action through a single endpoint with the operation named in the request, so scope the agent to the operations it needs, such as creating a configuration set or a receipt rule. Destructive operations like deleting a receipt rule set stay out of that set unless you add them. - **Credential handling:** Your AWS access keys for SES are stored once, encrypted, by your own Jentic One instance and injected at execution time when the request is signed. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'send a transactional email' or 'create a receipt rule', and Jentic returns the matching SES operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Amazon Pinpoint Email** — Pinpoint Email exposes a similar email-sending surface focused on marketing journeys - **Amazon EventBridge** — Routes SES delivery, bounce, and complaint events into downstream automation - **AWS Lambda** — Processes SES inbound email actions and bounce notifications ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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. ### Can I limit what my agent is allowed to do with the Amazon SES API? Yes. Because you run Jentic One yourself, your own rules decide which SES operations and credentials the agent may use. Since SES dispatches every action through a single endpoint with the operation named in the request, you scope the agent to only the operations it needs, such as CreateConfigurationSet or CreateReceiptRule, while destructive actions like deleting a receipt rule set stay out of that set unless you add them.