canonical: https://jentic.com/apis/amazonaws.com/pinpoint-email

# AWS Amazon Pinpoint Email Service

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.

## For AI agents

Send transactional email and manage AWS sending identities, dedicated IP pools, configuration sets, and deliverability data through Amazon Pinpoint Email.

## Scope

Does not handle SMS, push notifications, or campaign segmentation - use for transactional email sending and email-channel reputation management only.

## Capabilities

- 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

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

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

## Key resources

- **Email** — Send transactional and outbound email messages
- **Identities** — Manage verified email-address and domain sending identities
- **ConfigurationSets** — Group sending settings and attach event destinations
- **DedicatedIpPools** — Manage dedicated IPs and pools used for outbound sending
- **DeliverabilityDashboard** — Reputation, domain statistics, and inbox placement test results
- **SuppressionList** — Account-level addresses suppressed due to bounces or complaints

## Why Jentic

- **Setup:** Wiring Pinpoint Email by hand means computing SigV4 HMAC signatures for every request, routing to the right regional email host, verifying sending identities, and building bounce and complaint handling yourself. Through Jentic you install once, import Amazon Pinpoint Email Service from the API Directory, store your AWS access keys once, and your agent calls it while signatures are produced per request for you.
- **Permission scoping:** You choose the operations the agent may call, so you can limit it to sending, such as the SendEmail path (/v1/email/outbound-emails) and reading identities, while destructive operations like deleting a configuration set or a dedicated IP pool are not included unless you add them. Where an operation names a resource in the URL path, like a configuration set event destination under /v1/email/configuration-sets/{ConfigurationSetName}/event-destinations, the rule stays scoped to the operations you grant.
- **Credential handling:** Your AWS access keys are stored once, encrypted, by your own Jentic One instance and used to compute a SigV4 signature per request. The raw secret access key never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'send a transactional email through AWS' or 'verify a new sending domain', and Jentic returns the matching Pinpoint Email operation with its input schema for FromEmailAddress, Destination, and Content so the agent calls the right endpoint directly.

## Related APIs

- **Amazon SES** — Amazon SES is the broader email platform; Pinpoint Email shares much of the underlying infrastructure with a different API surface
- **Amazon CloudWatch** — Stream Pinpoint Email events to CloudWatch and alert on bounce or complaint thresholds
- **AWS Resource Access Manager** — Share Pinpoint Email resources such as configuration sets across AWS accounts in an organization

## FAQ

### 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 with Jentic One, the self-hosted execution layer.

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

### Can I limit what my agent is allowed to do with the Amazon Pinpoint Email Service API?

Yes. Because you run Jentic One yourself, you decide which operations and credentials your agent can use, so you can restrict it to a narrow set such as sending through SendEmail at /v1/email/outbound-emails and reading identities via GET /v1/email/identities. Destructive operations, like deleting a configuration set or a dedicated IP pool, are not included unless you grant them. Where an operation names a resource in its path, such as an event destination under /v1/email/configuration-sets/{ConfigurationSetName}/event-destinations, the rule stays scoped to exactly the operations you allow.