Documented steps

Endpoint: https://email.{region}.amazonaws.com/v2/email/outbound-emails — SES is regional; the identity you send from must be verified in that same region
Sign requests with AWS SigV4 (easiest via an AWS SDK: SESv2 SendEmail); credentials need ses:SendEmail permission
Body: 'FromEmailAddress' (a verified identity), 'Destination' {ToAddresses/CcAddresses/BccAddresses — max 50 recipients total}, and 'Content'
'Content' is exactly one of: 'Simple' {Subject.Data, Body.Text.Data and/or Body.Html.Data, optional Attachments[]}, 'Raw' {Data: base64 MIME}, or 'Template' {TemplateName, TemplateData JSON string}
HTTP 200 returns 'MessageId' — store it; delivery outcomes arrive via SNS/CloudWatch/event destinations, not the API response
Docs: https://docs.aws.amazon.com/ses/latest/APIReference-V2/API_SendEmail.html

Known gotchas

Sandbox accounts can only send TO verified addresses or the SES mailbox simulator (success@/bounce@/complaint@simulator.amazonses.com); anything else is rejected (MessageRejected)
Unverified From identity → MailFromDomainNotVerifiedException / MessageRejected 400
Max message size is 10 MB by default via API (after base64); larger (up to 40 MB) requires the v2 API in regions where supported and may be bandwidth-throttled
TooManyRequestsException = you exceeded your per-second send rate (sandbox default: 1 msg/sec, 200/day) — throttle client-side to your account's quota (GetAccount returns it)
SigV4 signature errors (403) are usually region mismatch between the endpoint and the signing region
Template sends: TemplateName must exist in that region and TemplateData must be a valid JSON *string* — NotFoundException / rendering failures otherwise; rendering failures surface asynchronously as Rendering Failure events, not HTTP errors

Use the Amazon SP-API FBA Inbound v2024 API to create an inbound shipment plan and confirm a send-to-Amazon (STA) workflow

docs.aws.amazon.com · 5 steps · unrated

subscribe to amazon sp-api notifications via sqs or eventbridge

amazon-sp-api · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans

Send an email via the Amazon SES v2 API (SendEmail / POST /v2/email/outbound-emails)

Documented steps

Known gotchas

Related routes

Give your agent this knowledge — and 15,500+ more routes

Need this verified for your stack — or a route we don't have yet?