AWS Amazon Pinpoint Email Service
Browse all AWS APIs★ Only Publicly Available OpenAPI DocumentCommunicationsEmail Deliveryhmac42 EndpointsREST
For Agents
Send transactional email and manage AWS sending identities, dedicated IP pools, configuration sets, and deliverability data through Amazon Pinpoint Email.
Use for: I need to send a transactional email through AWS, Verify a new sending domain in Pinpoint Email, List all dedicated IP pools on my AWS account, Set up an event destination that streams bounces to SNS
Not supported: Does not handle SMS, push notifications, or campaign segmentation — use for transactional email sending and email-channel reputation management only.
Jentic publishes the only available OpenAPI specification for Amazon Pinpoint Email Service, keeping it validated and agent-ready. Pinpoint Email is a transactional and bulk email sending service for AWS that supports verified sending identities, dedicated IP pools, configuration sets with event destinations, and a deliverability dashboard. The API exposes 42 operations covering identity verification, dedicated IP management, suppression list control, deliverability monitoring, and the SendEmail call itself. It serves teams that need programmatic control of email infrastructure with detailed reputation and deliverability telemetry.
Install Jentic One Beta
Connect the Amazon Pinpoint Email Service to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Amazon Pinpoint 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Pinpoint Email Service API.
Send transactional or simple email payloads via SendEmail with from, to, and content blocks
Verify domain and email-address sending identities and check their DKIM and MAIL FROM status
Manage dedicated IP pools and warm-up settings to isolate sending reputation by stream
Configure event destinations on a configuration set to stream bounces, complaints, and deliveries
Inspect deliverability dashboard data including domain reputation and inbox placement test results
Manage account-level and identity-level suppression lists for hard bounces and complaints
Use Cases
Patterns agents use Amazon Pinpoint Email Service API for, with concrete tasks.
★ Transactional Email Sending
Send password resets, receipts, and other transactional messages from AWS using a verified domain or address. SendEmail accepts a Destination, FromEmailAddress, and Content (Simple or Raw), with optional ConfigurationSetName to enable event tracking. Combine with a configuration set that has an event destination to capture bounces and complaints in real time.
Call POST /v1/email/outbound-emails with FromEmailAddress 'noreply@acme.com', Destination.ToAddresses ['user@example.com'], Content.Simple.Subject 'Reset your password', and ConfigurationSetName 'transactional'
Sender Reputation Management
Track and protect domain reputation by combining dedicated IP pools, configuration sets, and the deliverability dashboard. Create a dedicated IP pool for high-volume traffic, attach it to a configuration set, then read GetDeliverabilityDashboardOptions and GetDomainStatisticsReport to monitor reputation, complaint rate, and inbox placement.
Call POST /v1/email/dedicated-ip-pools to create pool 'transactional-pool', then PUT /v1/email/configuration-sets/{name}/delivery-options to attach it
Bounce and Complaint Tracking
Stream every bounce, complaint, and delivery to SNS, Kinesis, or CloudWatch by attaching event destinations to configuration sets. Pair with the suppression list APIs to automatically skip recipients with prior hard bounces. Useful for high-volume senders who need real-time signals to prune their lists.
Call POST /v1/email/configuration-sets/{ConfigurationSetName}/event-destinations with EventDestinationName 'bounces', MatchingEventTypes ['BOUNCE','COMPLAINT'], and an SnsDestination ARN
AI Agent Email Sending Tool via Jentic
A workflow agent uses Jentic to discover Pinpoint Email's SendEmail operation, load its schema, and dispatch transactional messages with subject and body assembled from upstream tool outputs. Jentic stores AWS credentials in its vault and signs each call with SigV4; the agent only handles the message content and recipient list.
Use Jentic to search 'send a transactional email through aws', load SendEmail, and execute it with a verified FromEmailAddress and a single recipient
Key Endpoints
42 endpoints — jentic publishes the only available openapi specification for amazon pinpoint email service, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/v1/email/outbound-emails
Send a single email message
POST
/v1/email/identities
Create and start verification on a sending identity
POST
/v1/email/configuration-sets
Create a configuration set
POST
/v1/email/configuration-sets/{ConfigurationSetName}/event-destinations
Attach an event destination to a configuration set
POST
/v1/email/dedicated-ip-pools
Create a dedicated IP pool
GET
/v1/email/identities
List sending identities
POST
/v1/email/outbound-emails
Send a single email message
POST
/v1/email/identities
Create and start verification on a sending identity
POST
/v1/email/configuration-sets
Create a configuration set
POST
/v1/email/configuration-sets/{ConfigurationSetName}/event-destinations
Attach an event destination to a configuration set
POST
/v1/email/dedicated-ip-pools
Create a dedicated IP pool
GET
/v1/email/identities
List sending identities
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
AWS access keys are encrypted in the Jentic vault and SigV4 signatures are produced per request, so agents never see the raw secret access key.
Intent-based discovery
Agents search by intent (e.g., 'send a transactional email through aws') and Jentic returns SendEmail with its full request schema for FromEmailAddress, Destination, and Content.
Time to first call
Direct integration: 1-2 days for SDK setup, identity verification, IAM policy scoping, and bounce handling. Through Jentic: under 30 minutes once an identity is verified.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Amazon Pinpoint Email Service API through Jentic.
Why is there no official OpenAPI spec for Amazon Pinpoint Email?
AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon Pinpoint Email 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 Pinpoint Email API use?
The API uses AWS SigV4 HMAC request signing with an AWS access key ID and secret. Through Jentic, AWS credentials are stored in the vault and SigV4 signatures are computed per request, so the agent never receives raw secrets.
How do I send a transactional email with this API?
POST /v1/email/outbound-emails with FromEmailAddress (must be verified), Destination, and Content. Set ConfigurationSetName to attach event tracking. The address or domain must be verified via /v1/email/identities first.
What are the sending quotas for Pinpoint Email?
New AWS accounts start in the sandbox with a 200-message-per-24-hours cap and 1 message-per-second send rate. After production access is granted these quotas increase based on account history; check sending limits programmatically via the GetAccount equivalent on the related SES v2 API.
Can I track bounces and complaints through this API?
Yes. Create a configuration set, then POST /v1/email/configuration-sets/{ConfigurationSetName}/event-destinations with MatchingEventTypes ['BOUNCE','COMPLAINT','DELIVERY'] and an SNS, Kinesis Firehose, or CloudWatch destination.
How do I send email through Jentic?
Search Jentic for 'send a transactional email through aws', load the SendEmail operation, and execute it with a verified FromEmailAddress and the recipient list. Install with pip install jentic; AWS credentials are pulled from the vault.
GET STARTED