Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Communications / Amazonaws / Amazon Simple Email Service
Amazon Simple Email Service logo

AWS Amazon Simple Email Service

Browse all Amazonaws APIs
32
AI ReadinessNon-Ready (F)32/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticCommunicationsEmail DeliveryapiKey142 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

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

Use for: I need to send a transactional email from a verified domain, Verify a new domain identity for SES, Set up a configuration set that publishes bounces to SNS, List all verified email identities in this region

Not supported: Does not handle SMS, push notifications, voice messages, or campaign segmentation - use for email sending and receiving via SES only.

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.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Amazon Simple Email Service to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Amazon Simple Email Service, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famazonaws.com%2Famazon-ses" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Famazonaws.com%2Famazon-ses" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

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

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

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

POST

/#Action=CreateCustomVerificationEmailTemplate

Create a custom verification email template

POST

/#Action=CloneReceiptRuleSet

Clone an existing receipt rule set

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

A

Amazon Simple Email Service

- Non-Ready (F)
32/100
98
Foundational Compliance
60
Developer Experience & Jentic Compatibility
12
AI-Readiness & Agent Experience
70
Agent Usability
50
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
98

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4
93%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

60

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: C+Signals: 4
1%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

38%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

12

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
47%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

0%

Summary Coverage

Coverage of summaries across operations/tags/info.

70

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A-Signals: 1
70%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

50

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1
50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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

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 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.

GET STARTED

Start building with Amazon Simple Email Service API

Explore with Jentic One
View OpenAPI Document